[PATCH, GCC] assorted autoconf updates
Ralf Wildenhues
Ralf.Wildenhues@gmx.de
Sat Jun 7 18:21:00 GMT 2008
More information about the Binutils mailing list
Sat Jun 7 18:21:00 GMT 2008
- Previous message (by thread): [PATCH, GCC] assorted autoconf updates
- Next message (by thread): [PATCH, GCC] assorted autoconf updates
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Daniel Jacobowitz wrote on Sat, Jun 07, 2008 at 03:55:56PM CEST: > On Sat, Jun 07, 2008 at 10:15:46AM +0200, Ralf Wildenhues wrote: > > * Ralf Wildenhues wrote: > > > Analogous post for binutils coming up. > > > > Log entries and diff for binutils. > > > > I have built binutils with this but done no further testing of any form. > > OK to apply? > > Yes. I have one question, though. Thanks. I'll apply when I have an OK for GCC as well. > > +dnl This file should be a no-op for the newest Autoconf version. > > +dnl Its bits can be removed once the complete tree has moved to a > > +dnl new enough Autoconf version. > > > +dnl Ensure exactly this Autoconf version is used > > +m4_define([_GCC_AUTOCONF_VERSION], [2.59]) > > + > > +dnl Test for the exact version when AC_INIT is expanded. > > These bits are in the same file but won't we want to keep the latter > after an upgrade? Yes, you are right, sorry about the sloppy comment. What about if I change it to this? dnl The override bits of this file should be a no-op for the newest dnl Autoconf version, which means they can be removed once the complete dnl tree has moved to a new enough Autoconf version. dnl dnl The _GCC_AUTOCONF_VERSION_TEST ensures that exactly the desired dnl Autoconf version is used. It should be kept for consistency. Cheers, Ralf
- Previous message (by thread): [PATCH, GCC] assorted autoconf updates
- Next message (by thread): [PATCH, GCC] assorted autoconf updates
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list