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 0/27] RFC: Use automake-1.11.6 across the tree


On 05/05/2015 10:03 AM, 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

[ ... snip ... ]
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

Are there any cases where you had to do something other than just regenerate the various files? If not, then as long as you fix the ChangeLog entries per Jakub's comments and ensure that you've also tested Ada, then this can be installed into the trunk. Do you have write access to the repository?

jeff


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