Re: [bug-gnulib] New GNULIB glob module?

[Derek Price]

Paul Eggert wrote:

>>There is one change I know I made that might have an effect.  I added
>>the "!defined _LIBC" to the following block because I was unsure what
>>__REDIRECT_NTH was supposed to be doing
>>    
>>
>
>I think that one's OK.
>  
>

Larry Jones on the CVS team just made a comment that makes me wonder if
it is, at least if we still plan on sharing this header with glibc... 
isn't the conversion to 64 bit file sizes and offsets supposed to be
transparent and handled by compile-time magic?

So, all the HAVE_.*64 stuff in glob.c shouldn't be necessary when !_LIBC.

Also, this particular bit in glob_.h would need to be used when !_LIBC
as well, since user-space programs compiling against the glob.h system
header from glibc would want glob64 used as compile-time magic, correct?

Please excuse me if this is way off, I don't have much experience at the
64-bit file offset stuff, myself.  One thing that leads me to believe I
may be wrong is that it looks like the glob64 from glibc 2.3.5 is only a
stub function.

Regards,

Derek