Re: dirname module calls AC_LIBOBJ unconditionally

2005-12-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 12/23/2005 5:05 AM: > Eric Blake wrote: > >>So experience in gnulib has shown that slightly different semantics, >>with dir_name that always mallocs, and (when my patch from a >>month ago is approved) base_name that malloc

Re: dirname module calls AC_LIBOBJ unconditionally

2005-12-23 Thread Jim Meyering
[EMAIL PROTECTED] (Eric Blake) wrote: > So experience in gnulib has shown that slightly different semantics, > with dir_name that always mallocs, and (when my patch from a > month ago is approved) base_name that mallocs and last_component As far as I know, we're still waiting for confirmation from

Re: dirname module calls AC_LIBOBJ unconditionally

2005-12-22 Thread Eric Blake
> The gl_DIRNAME macro (in dirname.m4) calls AC_LIBOBJ([dirname]) > unconditionally, without testing for a working dirname implementation. The dirname module provides dir_name and base_name, not dirname and basename. The reason for this is that POSIX does not allow dirname() or basename() to mall

dirname module calls AC_LIBOBJ unconditionally

2005-12-22 Thread Claudio Jolowicz
The gl_DIRNAME macro (in dirname.m4) calls AC_LIBOBJ([dirname]) unconditionally, without testing for a working dirname implementation. Also, the dirname module provides a basename implementation, but there is no basename.m4 that would test for this specific function. I need to provide a replaceme