On Sun, Aug 13, 2017 at 3:52 PM, Daniel Santos <daniel.san...@pobox.com> wrote:
> I've setup an x32 test environment using Gentoo in hopes of being able
> to both compile and run x32 tests, but I'm having problems getting a
> successful bootstrap.  I'm guessing this is due to something currently
> broken with x32, but I want to make sure it's not something I'm doing
> wrong, and if it is broken that we are aware of it.
>
> I'm able to get a 7.1 bootstrap using:
>
> /home/daniel/proj/sys/gcc/7.x/configure
> --prefix=/home/daniel/local/gcc-7.1.0 --build=x86_64-pc-linux-gnux32
> --with-abi=mx32 --enable-checking=yes,rtl --enable-languages=all
> --enable-bootstrap --enable-option-checking --enable-lto
> --enable-gold=yes --with-system-zlib --enable-link-mutex
> --enable-libgomp --enable-targets=all --disable-gcj

No need to build x32 GCC.  Just enable x32 run-time in x86-64 GCC
with

-with-multilib-list=m32,m64,mx32

is sufficient.

> (I guess --disable-gcj was probably useless now)
>
> But when I configure the same way from the head (from two days ago), it
> fails on stage2:
>
> /home/daniel/proj/sys/gcc/unpatched/configure
> --prefix=/home/daniel/local/gcc-unpatched --build=x86_64-pc-linux-gnux32
> --with-abi=mx32 --enable-checking=yes,rtl --enable-languages=all
> --enable-bootstrap --enable-option-checking --enable-lto
> --enable-gold=yes --with-system-zlib --enable-link-mutex
> --enable-libgomp --enable-targets=all --disable-gcj

x32 GCC built fine on trunk on Aug. 10 with

configure --with-demangler-in-ld
--enable-languages=c,c++,fortran,lto,objc,obj-c++,go
--prefix=/usr/gcc-8.0.0-mx32 --with-local-prefix=/usr/local
--enable-gnu-indirect-function --enable-clocale=gnu --with-system-zlib
--enable-libmpx --with-multilib-list=m32,m64,mx32
--enable-linker-build-id --enable-gnu-unique-object --with-abi=mx32
--with-fpmath=sse
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu

I didn't use  --build=x86_64-pc-linux-gnux32

-- 
H.J.

Reply via email to