This is the mail archive of the gcc-patches@gcc.gnu.org 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 build/doc] Replacing libiberty with gnulib


On Sun, 28 Aug 2016, ayush goel wrote:

> > > +AUTOCONF_VERSION="2.69"
> > > +AUTOMAKE_VERSION="1.15"
> > > +ACLOCAL_VERSION="$AUTOMAKE_VERSION"
> > > +
> >
> > Is there a reason these need to be different from what the rest
> > of the toolchain uses?
> 
> Not really, these were just the newer version.
> On the other hand is there a specific reason we are using older
> versions of these tools, despite newer versions being available.

Upgrading and testing in a range of different configurations, for all the 
packages sharing the toplevel code, is quite tricky (though it's libtool 
that's the most problematic and where we know that on any upgrade we need 
to revert a libtool change for sysroot handling that conflicts with GCC 
sysroot handling).

-- 
Joseph S. Myers
joseph@codesourcery.com


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