Mail Archives: cygwin/2003/01/06/11:55:32
Christian Jönsson wrote:
> When trying to configure/build binutils' cvs trunk sources I get a
> problem with running the autoconf script. A reply on binutils' list
> claims this to be a problem of cygwin's autoconf wrapper script.
One could easily say that the problem is binutils' configure.in, once it
was converted from "This is not an autoconf input script" to an actual
autoconf (2.13) input script, didn't include "AC_PREREQ(2.13)".
>>Are we on the road to 2.5x?
> No. This is a problem in your system's wrapper.
Yes, they ARE on the road to 2.5x. Nathanael Nerode and others have
been working for months now on that conversion. It is partially done --
but they are standardizing on 2.54? or something, NOT 2.57.
In addition, our wrapper defaults to 2.5x (in this case, 2.57) when the
appropriate version is not specified inside configure.in with an
AC_PREREQ() statement.
Daniel is saying that "All wrapper scripts should default to 2.13" which
is bullsh*t. It's his opinion against mine. Mine has worked damn well
for over two years. What's his track record?
> Is that script generic or is it cygwin specific?
The script is "generic" in the sense that I use it without modification
on Linux. However, nobody else does. AFAIK, it's only widely used on
cygwin.
I noticed that Mandrake 9.0 uses a similar scheme for autodetecting the
"desired" version of autoconf, so that ac-2.13 and ac-2.53(?) can
coexist. However, they do not also use wrappers for automake and
libtool, like cygwin does, and mandrake's wrapper is quite different
from ours.
Oh yeah -- mandrake defaults to 2.13; but that's because they treat the
2.5x branch somewhat differently than cygwin. On mandrake, 2.13 is
still the standard. On cygwin, the older versions of autotool don't
support our platform very well -- esp. libtool. Newer libtools (e.g.
CVS) that well-support cygwin, depend on automake-1.7.1 or newer...which
in turn depends on autoconf-2.5x.
So naturally, our wrapper scripts default to the versions which better
support our system.
> If it's cyginw specific perhaps it could be addressed here??
How about submitting this as a patch to the binutils people, with the
argument that "to avoid problems when wrapper scripts default to 'the
wrong version', let's explicitly require the correct version in each
configure.in, and change them from 2.13 to 2.5x as progress is made"
('course, you'll need to test it first; I haven't).
--Chuck
--- configure.in.orig 2003-01-06 11:46:34.000000000 -0500
+++ configure.in 2003-01-06 11:45:06.000000000 -0500
@@ -19,6 +19,7 @@
### WARNING: this file contains embedded tabs. Do not run untabify on
this file.
AC_INIT(move-if-change)
+AC_PREREQ(2.13)
AC_CANONICAL_SYSTEM
AC_ARG_PROGRAM
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -