[ENBD] 2GB limit on x86 hardware

[Peter T. Breuer]

"A month of sundays ago Staffan.Ohman@nokia.com wrote:"
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> > #include "confdefs.h"
> > #include <assert.h>
> >     /* Override any gcc2 internal prototype to avoid an error.  */
> >     /* We use char because int might match the return type of a gcc2
> >      builtin and then its argument prototype would still apply.  */
> > char lseek64();
> > int main() {
> >         /* The GNU C library defines this for functions which it
> >          * implements to always fail with ENOSYS.  Some 
> > functions are actually
> >            named something starting with __ and the normal name is an
> >            alias.  */
> >    #if defined (__stub_lseek64) || defined (__stub___lseek64)
> >         choke me
> >    #else
> >        lseek64();
> >    #endif
> > ; return 0;
> > }
> > 
> > So see how that compiles for you. Alternatively, remake the configure
> > script by running autoconf.
> > 
> Complains about not being able to find confdefs.h

Oops. Probably, yes. Make an empty confdefs.h file! I was
transliterating from the shell script.

> If I change the first line to #include "config.h" gcc doesn't say anything.

It always says something (but you have to ask it). In other words it
compiles, yes? Ok, good news.

> I think, however, I've found the reason for why make config failed to
> generate
> the correct config.h file for me. There is already a config.cache file
> present
> in the tarball. If you first say make distclean (or rm nbd/config.cache) and
> then make config both llseek and lseek64 are detected. 
> (and apparently lseek64 is used since the warning message about llseek
> disappears)
> I realize that only newbies like myself fail to see that right away, 
> but perhaps the person who creates the tarballs could
> rip out the config.cache file before putting it on the ftp server :)

:-). Yes. The problem is that the "current" tarballs are made by an automatic
process most times. They just snapshot the working area. I don't want
make distclean run on my working area! It is my fault, however, I most
certainly agree. I'll try and remember to do a make distclean before
letting really "official" things out. Now I'll see if there are any tars I
need to remake ...



Peter