[patch 0/27] RFC: Use automake-1.11.6 across the tree

[Bernd Edlinger]

Hi Michael,

On Thu, 7 May 2015 18:52:52, Michael Haubenwallner wrote:
>
> Hi Bernd,
>
> On 05/06/2015 03:01 PM, Bernd Edlinger wrote:
>> On Tue, 5 May 2015 18:03:15, Michael Haubenwallner wrote:
>>>
>>> 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
>>>
>>
>> And for completeness: ada missing here?
>
> This starts to become tricky here on my quite up-to-date Gentoo stable amd64 box:
>
> The normal host compiler is: gcc version 4.8.4 configured to --enable-languages=c,c++
> while the gnat compiler is: gnatgcc version 4.3.5 configured to --enable-languages=c,ada
>
> But: How do I tell the gcc-trunk/configure to use gcc/g++ for C/C++ and gnatgcc for Ada?
>
> I've thought of using CC=gnatgcc, but then I also would need something like CXX=gnatg++
> OTOH, seems like Gentoo never has enabled ada for the normal host gcc.
>
> Is this a problem I should fix with Gentoo, or is it me missing anything here?
>
> Thanks!
> /haubi/
>
> $ gcc -v
> Using built-in specs.
> COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrapper
> Target: x86_64-pc-linux-gnu
> Configured with: /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++-v4 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python --enable-languages=c,c++ --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --disable-nls --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4 p1.4, pie-0.6.1' --enable-libstdcxx-time --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-altivec --disable-fixed-point --en
> able-targets=all --disable-libgcj --enable-libgomp --disable-libmudflap --disable-libssp --disable-libquadmath --enable-lto --without-cloog --enable-libsanitizer
> Thread model: posix
> gcc version 4.8.4 (Gentoo 4.8.4 p1.4, pie-0.6.1)
>
> $ gnatgcc -v
> Using built-in specs.
> Target: x86_64-pc-linux-gnu
> Configured with: /var/tmp/portage/dev-lang/gnat-gcc-4.3.5/work/gcc-4.3.5/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gnat-gcc-bin/4.3 --includedir=/usr/lib64/gnat-gcc/x86_64-pc-linux-gnu/4.3/include --libdir=/usr/lib64/gnat-gcc/x86_64-pc-linux-gnu/4.3 --libexecdir=/usr/libexec/gnat-gcc/x86_64-pc-linux-gnu/4.3 --datadir=/usr/share/gnat-gcc-data/x86_64-pc-linux-gnu/4.3 --mandir=/usr/share/gnat-gcc-data/x86_64-pc-linux-gnu/4.3/man --infodir=/usr/share/gnat-gcc-data/x86_64-pc-linux-gnu/4.3/info --program-prefix=gnat --enable-languages=c,ada --with-gcc --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-nls --with-system-zlib --disable-checking --disable-werror --disable-libgomp --disable-libmudflap --disable-libssp --disable-libunwind-exceptions --enable-libada --enable-threads=gnat --enable-shared=boehm-gc,ada,libada --enable-multilib --enable-__cxa_atexit --enable-clocale=gnu
> Thread model: gnat
> gcc version 4.3.5

Hmm...

I don't think the boot strap can work if the "gcc" driver program does not
understand ada and c++ at the same time.

This can be a bit tricky:  If you can not find a working gcc with ada and c,c++
for your machine, then you will need to boot-strap that on a different host first.
That is possible, if you copy the so called system root files, that is all the necessary
glibc headers, and glibc binaries from your target system to $PREFIX/x86_64-pc-linux-gnu/include
and $PREFIX/x86_64-pc-linux-gnu/lib on the build-maching after binutils install but before
gcc boot-strap begins.


Bernd.