This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Libtool/Autoconf incompatibility issue

Hash: SHA1

According to Joseph S. Myers on 3/2/2008 3:37 PM:
| On Sun, 2 Mar 2008, Ralf Wildenhues wrote:
|> This is a mere defensive patch.  If (parts of) GCC or binutils happen to
|> use the next Autoconf, 2.62, by error or intention, without previously
| Is it possible to put something in the files to make Autoconf
| give an error if any version other than exactly 2.59 is used, to ensure
| that a newer version is only used as part of a deliberate coordinated
| update rather than accidentally in an individual directory?

Absolutely.  I don't know whether I recommend doing so in general, as it
makes the upgrade path a bit harder when gcc is finally ready to move on
to more modern tools, but since gcc checks in the generated file, I think
it makes sense.  This will work with 2.59:

m4_if([2.59], m4_defn([m4_PACKAGE_VERSION]), [],
~      [m4_fatal([Please use exactly Autoconf 2.59])

- --
Don't work too hard, make some time for fun as well!

Eric Blake   
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]