Eric Blake writes:
> Marking a macro obsolete in autoconf means that new code should not rely
> on it, but that the macro still exists and still does the same thing it
> used to do, so that old code that used it will continue to work.
Oh, okay, I misunderstood obsolete. Never mind, then. :)
-
.
+
+ AC_FUNC_ERROR_AT_LINE AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK
+ AC_FUNC_MKTIME AC_FUNC_STRTOD
If that gets accepted in Autoconf, here is a proposed patch for gnulib, in
order to take over the maintenance of these macros from Autoconf (and also of
AC_FUNC_MEMCMP, which was already marked
- AC_FUNC_OBSTACK
- AC_FUNC_STAT, AC_FUNC_LSTAT
- AC_FUNC_STRTOD
- AC_FUNC_STRNLEN
- AC_REPLACE_FNMATCH
This seems like a reasonable plan to me, but if you do this, the one
additional request I have is to please retain somewhere in the Autoconf
documentation a mention that these functions have known
On 08/28/2010 03:56 AM, Bruno Haible wrote:
2010-08-28 Bruno Haible
* doc/autoconf.texi (Particular Functions): Mark AC_FUNC_ERROR_AT_LINE,
AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK, AC_FUNC_MKTIME, AC_FUNC_STRTOD
as obsolete and refer to Gnulib.
* NEWS: Mention the
Hello Bruno,
* Bruno Haible wrote on Sat, Aug 28, 2010 at 12:56:21PM CEST:
> Paolo Bonzini wrote on 2010-06-15:
> > >- AC_FUNC_STRNLEN
> >
> > This maybe falls in the same group as AC_FUNC_MALLOC/AC_FUNC_REALLOC.
>
> OK, let's leave it in Autoconf. But the cross-compilation guess is too
> p
Paolo Bonzini wrote on 2010-06-15:
> >- AC_FUNC_STRNLEN
>
> This maybe falls in the same group as AC_FUNC_MALLOC/AC_FUNC_REALLOC.
OK, let's leave it in Autoconf. But the cross-compilation guess is too
pessimistic for gnulib habits: we haven't seen the AIX bug on any system
except on AIX. In
FUNC_ERROR_AT_LINE AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK
> + AC_FUNC_MKTIME AC_FUNC_STRTOD
If that gets accepted in Autoconf, here is a proposed patch for gnulib, in
order to take over the maintenance of these macros from Autoconf (and also of
AC_FUNC_MEMCMP, which was already marked obsolescent)
in this, you're likely using gnulib anyway nowadays.
>
> >- AC_FUNC_STRTOD
> >- AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK
> >- AC_FUNC_MKTIME
> >- AC_FUNC_STAT, AC_FUNC_LSTAT
> >- AC_FUNC_GETLOADAVG
> >- AC_REPLACE_FNMATCH
>
AC_FUNC_REALLOC, because the replacement
code for them is so trivial that anyone can make it up himself.
Agreed.
The affected macros are:
- AC_FUNC_ERROR_AT_LINE
If you're interested in this, you're likely using gnulib anyway nowadays.
>- A
- AC_FUNC_OBSTACK
> - AC_FUNC_STAT, AC_FUNC_LSTAT
> - AC_FUNC_STRTOD
> - AC_FUNC_STRNLEN
> - AC_REPLACE_FNMATCH
This seems like a reasonable plan to me, but if you do this, the one
additional request I have is to please retain somewhere in the Autoconf
documentation a mention that t
On 06/14/2010 01:56 PM, Bruno Haible wrote:
>> Or even better, why not push those two tests upstream into autoconf,
>> then have gnulib override AC_FUNC_STRTOD if it detects older autoconf,
>> so that everyone using upstream AC_FUNC_STRTOD can reliably detect these
>> same
Hi Eric,
> > With two old old old tests and no reasonable cross-compiling behaviour I
> > would say that the best thing to do is to move these two blocks of C
> > code
> > into gl_FUNC_STRTOD's test, and stop using AC_FUNC_STRTOD. Then the
> > a
12 matches
Mail list logo
