On Thu, 2014-03-27 at 13:36 +0800, Chung-Ju Wu wrote:
> 2014-03-26 18:24 GMT+08:00 Svante Signell <svante.sign...@gmail.com>:
> > Hi,
> >
> > With the recent changes of not using automake for the build, only
> > auto{re}conf I have problems generating an updated Makefile.in from a
> > modified Makfile.am. Source is gcc-4.9-4.9-20140322
> >
>
> For gcc-4.9, I always use automake-1.11.1 and autoconf-2.64
> to regenerate 'configure' and 'Makefile.in' content.
Thanks, I downgraded to automake-1.11.1 and autoconf-2.64 and started
with a fresh install of Debian gcc-4.9-4.9-20140322.
Creating src/libgo/Makefile.in from Makefile.am only issued warnings:
(cd src/libgo;automake)
testsuite/Makefile.am:6: user variable `EXPECT' defined here...
/usr/share/automake-1.11/am/dejagnu.am: ... overrides Automake variable
`EXPECT' defined here
testsuite/Makefile.am:10: user variable `RUNTEST' defined here...
/usr/share/automake-1.11/am/dejagnu.am: ... overrides Automake variable
`RUNTEST' defined here
** I see one big problem with only autoconf2.64 being run when building:
All Makefile.in files have to be patched in addition to Makefile.am when
making changes, complicating things a lot!
Two questions/comments:
- When will gcc switch to use the latest versions of autoconf (2.69) and
automake (1.14) for it's build system? autoconf 2.64 and automake 1.11
are old by now, 26-Jul-2009 and 08-Dec-2009. Many distributions don't
have them any longer. For example for autoconf 2.65 in Debian you have
to use snapshot.debian.org. (up till now, there are specific versions
available: autoconf2.64 and automake1.11 (1.11.6))
- In an ideal situation no generated files should be shipped with a
distribution, i.e. only configure.ac and Makefile.am, no configure,
Makefile.in Makefile when not needed!
