search for: _file_offset_bits

I didn't see this one applied to the repository yet. It may not be the best patch possible... basic problem is that _LARGEFILE64_SOURCE needs to be defined on Solaris 2.6 if AC_SYS_LARGEFILE ends up doing a '#define _FILE_OFFSET_BITS 64' If _FILE_OFFSET_BITS == 64, then <sys/resource.h> will define a 'struct rlimit64' but NOT define a 'struct rlimit' leading to a failure to compile ssh.c because 'struct rlimit' is not a complete type. When _LARGEFILE64_SOURCE is defined, it adds a #define rli...

How do I activate this flag in ./configure? I don't have an AMD 64 processor... is this just for that? checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64

On 2014?05?12? 22:38, H. Peter Anvin wrote: > That is because it needs to use fseeko() and use off_t. Do you mean it does need a patch for isohybrid.c. And the patch looks like: #if _FILE_OFFSET_BITS == 64 fseeko(...) #else fseek(...) Regards, Kai > > On May 11, 2014 11:53:17 PM PDT, Kang Kai <Kai.Kang at windriver.com> wrote: >> On 2014?05?12? 10:49, H. Peter Anvin wrote: >>> On 05/11/2014 06:56 PM, Kai Kang wrote: >>>> When call isohybrid wit...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 configure:17280: result: no configure:17300: checking for mblen configure:17356: gcc -o conftest -O3 -m64 -mtune=native -pipe -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset

...ade, making me unable to compile dovecot the usual way so I am seeking a 3rd eye. The config.log is at : http://bit.ly/2jE5djl Hoping someone can help me figure out what is broken. During configure, it fails with: checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... unknown checking for _LARGE_FILES value needed for large files... unknown checking for _Bool... yes checking for uoff_t... no checking type of off_t... unknown configure: error: Unsupported off_t type -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200...

Hi, I tried to compile rsync-2.5.2 on Solaris 5.7 Ultra-2 machine, 5.7 on Ultra-2 is running 64 bit, but, when I ran configure, it said no for largefile, I thought 2.5.2 will support large file? Is that true? Thanks, Jennifer

...-image-x86-64-20140505110100.iso: seek error - 8: Invalid argument >> >> Check the offset and call fseek() multi-times if offset is too large. >> >> Signed-off-by: Kai Kang <kai.kang at windriver.com> > NAK. > > The right thing to do is compile it with #define _FILE_OFFSET_BITS 64 > and change fseek to fseeko with the appropriate type being off_t. > > -hpa Hi hpa, Thanks for your reply. In utils/Makefile, -D_FILE_OFFSET_BITS=64 is added to CFLAGS. isohybrid is compiled with -D_FILE_OFFSET_BITS=64 but it still fails to handle the large offset. make[3]: Ente...

Hi, I suggest to add the following definition to configure and its template configure.in to allow samba-2.2.x to be compiled on HP/UX 11.00 with some lesser warnings. Without this definition you'll get warnings on all socket operation because the socket operations are UNIX98 specific and HP/UX 11.00 will support this when _XOPEN_SOURCE_EXTENDED is defined. -- Ren? Nieuwenhuizen Afdeling

I was trying to install ferret 0.9.2 on solaris (SunOS 5.8) which does not have a sys/dir.h nix_io.c:5:21: sys/dir.h: No such file or directory make: *** [nix_io.o] Error 1 I couldn''t find an obvious way around this... any suggestions? Thanks, Rich Marisa Cornell Information Technologies Cornell University

...; http://msdn.microsoft.com/en-us/library/0ys3hc0b%28v=vs.110%29.aspx That's not enough. At least, the followings are also needed. 1. Change off_t to something else. off_t can lead to ABI issue when used in public API, since it's definition can change even on the same system (by setting _FILE_OFFSET_BITS or something), and is always 32bit on mingw, mingw-w64 and MSVC. Since FLAC even takes the trouble of casting seek offset to off_t when calling fseeko(), it gets truncated to 32bit on Win32 even if you use _fseeki64(). This change results in ABI break, but luckily it seems there's only one...

When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: wrlinux-image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Check the offset and call fseek() multi-times if offset is too large.

In glibc 2.10 (32 bit) fallocate() exists but fallocate64() doesn't. When _FILE_OFFSET_BITS==64, fallocate() is a redirect to fallocate64() and the program can't be linked (fails to find symbol fallocate64). See http://bugzilla.redhat.com/500487 Attached patch detects fallocate() more robustly to guard against this problem. Cheers, Paul. -------------- next part -------------- A non...

.... On May 12, 2014 6:26:18 PM PDT, Kang Kai <Kai.Kang at windriver.com> wrote: >On 2014?05?12? 22:38, H. Peter Anvin wrote: >> That is because it needs to use fseeko() and use off_t. > >Do you mean it does need a patch for isohybrid.c. And the patch looks >like: > >#if _FILE_OFFSET_BITS == 64 > fseeko(...) >#else > fseek(...) > > >Regards, >Kai > >> >> On May 11, 2014 11:53:17 PM PDT, Kang Kai <Kai.Kang at windriver.com> >wrote: >>> On 2014?05?12? 10:49, H. Peter Anvin wrote: >>>> On 05/11/2014 06:56 PM, Kai...

...ert Stappers > You will see the recent commits, including the 'fseek' to 'fseeko' change. I was looking at http://git.kernel.org/cgit/boot/syslinux/syslinux.git which is what Google brings up on "syslinux git" and looks quite official. Now i wonder about +#define _FILE_OFFSET_BITS 64 after it was already done in Makefile some time earlier. Luckily, elsewise my local copy was up to date. > > [statements about off_t and fseeko(3)] > Please convert that into patches to the mailinglist. I got six patches now. The end version compiles and can run standalone without h...

Hi, hpa: > The right thing to do is compile it with #define _FILE_OFFSET_BITS 64 > and change fseek to fseeko with the appropriate type being off_t. And for GPT names it should really use 16-bit UTF-16LE characters and not 8-bit characters padded up by the same number of random bytes from the program memory. See e.g.: http://git.kernel.org/cgit/boot/syslinux/syslinux.g...

...ICIT_LARGEFILE_SUPPORT 1 . . . #define HAVE_READDIR64 1 . . . -------------------------------------------------------------------------------- >From Makefile: -------------------------------------------------------------------------------- . . . CPPFLAGS= -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 . . . -------------------------------------------------------------------------------- If you add "-E" to CFLAGS in the Makefile, you can see the code produced is: . . . extern struct dirent * readdir64 (DIR *); . . . struct dirent64 *sys_readdir(DIR *dirp);...

...e been trying to get rsync to work on AIX 4.3.3 with files > 2GB. I've looked through the archives and saw reference to this, etc. on HPUX but have not been able to come across a solution for AIX. I've tried compiling with the following flags without luck: "-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" There error I'm getting is as follows (when hitting the 2GB limit): rsync: error writing 32768 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) When I run ./configure I see these lines pertaining to large file support...

...them to the same size, so I recompiled rsync to support large files support but I failed again: sh ./configure --enable-largefile --prefix=/usr In the output you can see: checking for broken largefile support... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for _LARGE_FILES value needed for large files... no $ rsync --version rsync version 2.5.6 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 32-bit files, socketpairs, hard links, sym...

Put this in the wrong thread, sorry! UPDATE: I've realized that this seems to be an issue with the compiler flags used to build samba. I've realized that i need to define _LARGEFILE_SOURCE, _LARGEFILE64_SOURCE, and _FILE_OFFSET_BITS=64. I've done this, but still have no luck reading files larger than 4GB. Anyone have suggestions? Thanks, Matt > Hi guys, > > I'm attempting to move large files (>4GB) from a PowerPC-based embedded system running a 2.4 kernel architecture to an PC running a 2.6 kernel. I&...

...rectories... /usr/lib/tcl8.5/tclConfig.sh checking for tkConfig.sh... no checking for tkConfig.sh in library (sub)directories... /usr/lib/tk8.5/tkConfig.sh checking whether compiling/linking Tcl/Tk code works... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking for _LARGEFILE_SOURCE value needed for large files... no checking whether KERN_USRSTACK sysctl is supported... no checking for cached Java settings... no checking for Fortran flag to compile .f90 files... none checking for Fortran flag to compile .f95...