[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #110397] autoconf 2.70: autotest.m4 error
From: |
FX |
Subject: |
[sr #110397] autoconf 2.70: autotest.m4 error |
Date: |
Sun, 13 Dec 2020 18:38:22 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.1 Safari/605.1.15 |
Follow-up Comment #11, sr #110397 (project autoconf):
Re. GNU m4, Apple has:
$ /usr/bin/m4 --version
GNU M4 1.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Rene' Seindal.
Indeed, autoconf's configure script concludes that it has "supports accurate
traces". Do you want me to run a test to double-check?
Re. the bigger picture: automake is trying to test whether autoconf is
functional by testing it on a simple .ac file:
$ cat conftest.ac
AC_INIT
$ /tmp/bin/autoconf -o /dev/null conftest.ac
unknown channel m4trace: -1- _m4_warn(syntax, AC_OUTPUT was never used, )
at /tmp/share/autoconf/Autom4te/Channels.pm line 631.
Autom4te::Channels::msg("m4trace: -1- _m4_warn(syntax, AC_OUTPUT was
never
used, )\x{a}", undef, undef, "partial", 0) called at /tmp/bin/autom4te line
1073
This content of conftest.ac is exactly what is being tested by configure, with
those exact options. I don't understand the "unknown channel m4trace" part,
but "AC_OUTPUT was never used" seems clear enough. The doc for AC_OUTPUT
states: "This is the only required macro besides AC_INIT".
Should, shouldn't automake simply include AC_OUTPUT in its simple test? I
mean, if I add it as a second line of conftest.ac, the test definitely passes.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110397>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [sr #110397] autoconf 2.70: autotest.m4 error, (continued)
- [sr #110397] autoconf 2.70: autotest.m4 error, Zack Weinberg, 2020/12/08
- [sr #110397] autoconf 2.70: autotest.m4 error, anonymous, 2020/12/08
- [sr #110397] autoconf 2.70: autotest.m4 error, Carlo Cabrera, 2020/12/08
- [sr #110397] autoconf 2.70: autotest.m4 error, Zack Weinberg, 2020/12/08
- [sr #110397] autoconf 2.70: autotest.m4 error, Carlo Cabrera, 2020/12/08
- [sr #110397] autoconf 2.70: autotest.m4 error, FX, 2020/12/09
- [sr #110397] autoconf 2.70: autotest.m4 error, Karl Berry, 2020/12/13
- [sr #110397] autoconf 2.70: autotest.m4 error, Carlo Cabrera, 2020/12/13
- [sr #110397] autoconf 2.70: autotest.m4 error, Karl Berry, 2020/12/13
- [sr #110397] autoconf 2.70: autotest.m4 error, Carlo Cabrera, 2020/12/13
- [sr #110397] autoconf 2.70: autotest.m4 error,
FX <=
- [sr #110397] autoconf 2.70: autotest.m4 error, Zack Weinberg, 2020/12/13
- [sr #110397] autoconf 2.70: autotest.m4 error, FX, 2020/12/14
- [sr #110397] autoconf 2.70: autotest.m4 error, Karl Berry, 2020/12/14
- [sr #110397] autoconf 2.70: autotest.m4 error, Karl Berry, 2020/12/14