From: Charles Wilson <cwilso11@us...> - 2011-10-10 20:42:00
I've uploaded two new packages, but they are probably of interest only
to developers of gcc itself; most users should ignore these packages.
Development of gcc requires specific unpatched versions of autoconf and
automake -- otherwise patches will be rejected by upstream gcc@... For
gcc-4.5 and 4.6, the required versions are:
However, installing these versions into /mingw/* would interfere with
the current autotools scheme. Therefore, as a convenience to gcc
developers who work in the MinGW environment (of which there may be only
one or two!) these two packages are provided. They install into
So gcc devs need only set PATH to ensure /mingw/opt/epoch2/bin precedes
the "normal" /mingw/bin directory.
(FYI, the forthcoming update of gettext, to version 0.18.1.1, also
requires these versions of the autotools. But that's of interest only to
people who wish to rebuild mingw32-gettext-0.18.1.1 itself from our -src
package, and has no impact on *users* of libintl).
To install these packages:
mingw-get install mingw32-gcc-tools-epoch2-autoconf
mingw-get install mingw32-gcc-tools-epoch2-automake
NOTE: the -src components are built using the new 'mgwport' tool. See
forthcoming announcement. But because mgwport works very hard to ensure
consistent "default" behavior -- such as compiling mingw packages for
the /mingw (C:\MinGW) prefix -- the -src packages here have to work
equally hard to defeat those defaults and install these packages into
/mingw/opt/whatever. Hence, I would not recommend using the .mgwport
scripts in these -src packages as examplars! *Regular* .mgwport scripts
are not nearly this ugly.
P.S. Why epoch2? Because these packages are based on their cygwin
analogs, and on cygwin the 'epoch1' packages were required for gcc-4.3
and gcc-4.4 development, and provided autoconf-2.59 and automake-1.9.6.