[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Andrew Suffield <address@hidden>] Bug#157887: autoconf: various imperfe
From: |
Ben Pfaff |
Subject: |
[Andrew Suffield <address@hidden>] Bug#157887: autoconf: various imperfectly formed functions in c.m4 |
Date: |
23 Aug 2002 09:16:58 -0700 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Hi. The following bug was reported against the Debian GNU/Linux
package for Autoconf 2.53. I am forwarding it upstream since its
complaints are out of the scope of Debian maintainership for a
package as I see it.
Thanks,
Ben.
-------------------- Start of forwarded message --------------------
Subject: Bug#157887: autoconf: various imperfectly formed functions in c.m4
Date: Fri, 23 Aug 2002 14:31:56 +0100
From: Andrew Suffield <address@hidden>
To: address@hidden
reopen 157887
thanks
On Thu, Aug 22, 2002 at 03:22:44PM -0700, Ben Pfaff wrote:
> Andrew Suffield <address@hidden> writes:
>
> > Package: autoconf
> > Version: 2.53-5
> > Severity: normal
> >
> > c.m4 contains several functions which are not correctly formed -
> > mostly undeclared argument lists. This causes unnecessary test
> > failures when running with -Wstrict-prototypes -Werror in CFLAGS.
>
> You shouldn't modify the CFLAGS that Autoconf uses. Only modify
> it for use in your own Makefiles. Otherwise, it's a bug in your
> configure.in, not in Autoconf.
Then I will have to override _all_ of the autoconf macros with my own
versions. I am not interested in what happens with the default
CFLAGS. Lots of parameters to gcc can and will modify its behaviour,
and I need to know what features are available under those conditions.
This is a grotesque flaw in autoconf; it just became vastly less
useful.
> Autoconf doesn't assume that the system C compiler supports ANSI
> prototypes.
Then it should test for that, not assume it is running K&R. I find the
"feature" of supporting K&R at the expense of ANSI to be rather less
than useful, especially since almost all the autoconf-using project
nowdays don't support K&R C anyway.
Additionally, if running with different CFLAGS is not supported,
there's a different bug: autoconf uses whatever value for $CFLAGS you
had set in the shell. Here's an example:
address@hidden:~/tmp$ cat configure.ac
AC_INIT(foo, 0.1)
AC_C_INLINE
AC_OUTPUT()
address@hidden:~/tmp$ autoconf
address@hidden:~/tmp$ CFLAGS="-Werror -Wstrict-prototypes -Wmissing-prototypes"
./configure
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot
create executables
Here autoconf has taken it upon itself to dictate what flags I can
use.
At least one of the above two things is a bug. I should be able to set
CFLAGS to whatever I want to compile with, and I need to know whether
I can (for example) use inline when a full set of warning flags are
enabled.
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ | Dept. of Computing,
`. `' | Imperial College,
`- -><- | London, UK
-------------------- End of forwarded message --------------------
--
"Long noun chains don't automatically imply security."
--Bruce Schneier
- [Andrew Suffield <address@hidden>] Bug#157887: autoconf: various imperfectly formed functions in c.m4,
Ben Pfaff <=