From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29084 invoked by alias); 13 May 2015 11:47:04 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 29057 invoked by uid 89); 13 May 2015 11:47:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 3 recipients X-HELO: smtp.salomon.at Received: from smtp.salomon.at (HELO smtp.salomon.at) (193.186.16.13) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 13 May 2015 11:47:00 +0000 Received: from samail03.wamas.com ([172.28.2.2] helo=mailhost.salomon.at) by smtp.salomon.at with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1YsV7j-0008R3-CQ; Wed, 13 May 2015 13:46:52 +0200 Received: from [172.28.41.34] by mailhost.salomon.at with esmtp (Exim 4.77) (envelope-from ) id 1YsV7j-0007Xb-6i; Wed, 13 May 2015 13:46:51 +0200 Message-ID: <555339AB.2090805@ssi-schaefer.com> Date: Wed, 13 May 2015 11:59:00 -0000 From: Michael Haubenwallner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Paolo Bonzini , DJ Delorie , Nathanael Nerode , Alexandre Oliva , Ralf Wildenhues CC: Jan-Benedict Glaw , GCC Patches , Bernd Edlinger , Janne Blomqvist , Kai Tietz Subject: [committed] [patch 0/27] Use automake-1.11.6 across the tree References: <5548E9C3.1090408@ssi-schaefer.com> In-Reply-To: <5548E9C3.1090408@ssi-schaefer.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-05/txt/msg01210.txt.bz2 On 05/05/2015 06:03 PM, Michael Haubenwallner wrote: > 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 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. Using automake-1.11.6 across the tree (except for libgo) is committed. >> * ...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: Commands used: $ /src/gcc-trunk/configure --prefix=/install \ --enable-languages=c,c++,fortran,go,java,lto,objc,obj-c++,ada \ --enable-liboffloadmic=target \ --enable-libmpx \ --enable-libada \ --enable-maintainer-mode $ make bootstrap Reverted changes to libffi/doc/version.texi (would bump VERSION 3.9999). Thanks! /haubi/