Hello build machinery maintainers,
following up
http://thread.gmane.org/gmane.comp.gcc.patches/331902/focus=334462
http://thread.gmane.org/gmane.comp.gcc.patches/332160
On 01/25/2015 08:42 PM, Jan-Benedict Glaw wrote:
> On Sun, 2015-01-04 20:20:40 +0100, Michael Haubenwallner
> <michael.haubenwall...@ssi-schaefer.com> wrote:
>> Updating to 1.14 might require more work like updating some .in
>> files as well. I've seen automake-1.11 being explicitly used, so for
>> now we really want 1.11.6 eventually?
>
> Probably yes, we may want to stick to a well-known version. (Maybe
> another way could be to really upgrade to current versions, with is, I
> guess, more work than just sync files and rerun. That might be
> fruitful (ie. to not stick to older versions), but this is a change I
> don't see in the current stage.)
>
> To cut a long story short:
>
> * Do we actually see *problems* from the version inconsistencies
> already introduced by me and/or others?
There's a problem for gcc-developers: When I need to import a libtool
upstream patch, by its nature it affects each library. As I prefer to
avoid mixing these diffs with an automake version change in one commit,
I need to bootstrap different libraries with different automake versions.
Even if I probably need to split this change into one commit per library
anyway, the need for multiple automake versions still feels pointless.
> * ...and: Do we want to stick to known versions, or update if?
> (Probably not in such a late stage, though...)
Now that gcc-5 is out, what about an automake-1.11.6 update for gcc-6?
BTW, the actual commands I use to re-run automake for everything (I found) is:
$ export AUTOMAKE='automake-1.11 --add-missing --copy --force-missing'
$ /src/gcc-trunk/configure --prefix=/install \
--enable-languages=c,c++,fortran,go,java,lto,objc,obj-c++ \
--enable-liboffloadmic=target \
--enable-libmpx \
--enable-maintainer-mode
$ make bootstrap
Thanks!
/haubi/
