Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> > - sys/socket.h is currently included. It is not needed on OpenBSD 3.4.
>> > But it is needed for 'socklen_t' to be defined portably, I think - look
>> > at socklen.m4.
>>
>> Strictly, I don't believe it is needed -- arpa/in
Simon Josefsson wrote:
> I installed this patch:
>
> Index: modules/socklen
> ===
> RCS file: /sources/gnulib/gnulib/modules/socklen,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -p -r1.2 -r1.3
> --- modules/socklen
[ I've checked in a pretty big (conceptually, at least) coreutils change
today. Here's some of the background and justification, along with
the actual patch. ]
I started my little cwd/thread-safety crusade with GNU rm. Fixing
the core function to be thread safe meant rewriting remove.c not
Simon Josefsson wrote:
> >> +#include
> >>
> >> License:
> >> unlimited
> >
> > Then 'socklen' should also have a dependency on 'sys_socket'.
>
> I'm not sure. It gets ugly if no modules can assume sys/socket.h
> without depending on sys_socket?
That's the point of the sys_socket module.
If y
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> I installed this patch:
>>
>> Index: modules/socklen
>> ===
>> RCS file: /sources/gnulib/gnulib/modules/socklen,v
>> retrieving revision 1.2
>> retrieving revision 1
On Tue, Jan 17, 2006 at 10:33:18PM +0100, Jim Meyering wrote:
> FTS API change:
> ==
>
> This changes the fts API.
Is there a way for autoconf-using gnulib client s to select only the
gnulib version? I'm happy to adopt the change, as long as I don;t run
the risk of having 'configur
>
> Is there a way for autoconf-using gnulib client s to select only the
> gnulib version? I'm happy to adopt the change, as long as I don;t run
> the risk of having 'configure' wrongly select the wrong fts()
> implementation.
Gnulib fts will not select any other fts implementation. Look at m4/
>
> FTS API change:
> ==
>
> This changes the fts API. Before, callers (those not using FTS_NOCHDIR)
> could expect fts_read to change the current working directory so that
> a simple directory entry name (fts_accpath) could be used to access
> files in the directory in question. No
Bruno Haible <[EMAIL PROTECTED]> writes:
> If you use the new 'ldd' module, it
> - should work also when cross-compiling,
> - should be immune to changed addresses in the output of 'chatr',
> 'dump -H', 'elfdump -Dl', 'ldd', 'odump -Dl',
> - simply feels safer to use the appropriate comm
