From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF' Date: Tue, 10 Jul 2018 21:51:15 +0200 Message-ID: <87601mna30.fsf@gnu.org> References: <87sh4sny8j.fsf@gnu.org> <5B43A955.7090904@mutluit.com> <87muv0nqoi.fsf@gnu.org> <5B442D84.8030805@mutluit.com> <87sh4rm8nb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org In-Reply-To: <87sh4rm8nb.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 10 Jul 2018 17:07:36 +0200") To: =?utf-8?Q?G=C3=A1bor?= Boskovits Cc: um@mutluit.com, gcc-help@gcc.gnu.org, Guix-devel List-Id: guix-devel.gnu.org Jan Nieuwenhuizen writes: > G=C3=A1bor Boskovits writes: > >> It seems that the errors you were getting are related to 128 bit >> floating point support. It also seems that 128 bit floating point >> support is enabled on 64 bits. I'm not sure about the 32 bit case >> though, do you get the same error there? =C2=A0 > > Ah! That makes me even more supicious... I was wondering about this > command > > i386-unknown-linux-gcc ... -DIN_GCC -o _muldi3.o -c ../.././libgcc/li= bgcc2.c > > this i386-unknown-linux-gcc compiler is the bootstrap compiler, > gcc-4.1.0 (or we may be able to use 2.95.3); is that OK? Shouldn't the > new `xgcc' compiler be used to compile libgcc2? Some great progress! I found the build-i686-pc-linux-gnu host-i386-unknown-linux build directories very suspicous. I found that in my bootstrap I used the older `i386-unknown-linux' only because I started with a very early binutils that didn't know about i686-*linux-gnu yet. So I have changed the entire bootstrap to use i686-unknown-linux-gnu and configure gcc-4.7.4 using ../build/configure --build=3Di686-unknown-linux-gnu --host=3Di686-unknown-linux-gnu --disable-decimal-float --disable-libatomic --disable-libcilkrts --disable-libgomp --disable-libitm --disable-libmudflap --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdcxx-pch --disable-libvtv --disable-lto --disable-lto-plugin --disable-multilib --disable-plugin --disable-shared --disable-threads --enable-languages=3Dc --enable-static --prefix=3D/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4 --with-build-sysroot=3D/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqdx5vfly-glib= c-mesboot-2.2.5/include --with-native-system-header-dir=3D/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqd= x5vfly-glibc-mesboot-2.2.5/include Now, building _muldi3.o from libgcc2.c passes, interestingly indeed the fresh `xgcc' compiler is used now /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/xgcc -B/t= mp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/ -B/gnu/store/m= khbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/bi= n/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unk= nown-linux-gnu/lib/ -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gc= c-mesboot-4.7.4/i686-unknown-linux-gnu/include -isystem /gnu/store/mkhbgqfp= j17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/sys-inclu= de --sysroot=3D/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqdx5vfly-glibc-mesboot-2.= 2.5/include -g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wcast= -qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isy= stem ./include -fpic -g -DIN_LIBGCC2 -fno-stack-protector -fpic -I. -I.= -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../g= cc -I../../../libgcc/../include -DHAVE_CC_TLS -DUSE_TLS -o _muldi3.o -MT = _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c ../../../libgcc/libgcc2.c= =20 no wonder it failed before. However, now i get this error (I do not have pthreads/pthreads.h). /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/xgcc -B/t= mp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/ -B/gnu/store/m= khbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/bi= n/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unk= nown-linux-gnu/lib/ -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gc= c-mesboot-4.7.4/i686-unknown-linux-gnu/include -isystem /gnu/store/mkhbgqfp= j17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/sys-inclu= de --sysroot=3D/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqdx5vfly-glibc-mesboot-2.= 2.5/include -g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wcast= -qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isy= stem ./include -fpic -g -DIN_LIBGCC2 -fno-stack-protector -fpic -I. -I.= -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../g= cc -I../../../libgcc/../include -DHAVE_CC_TLS -DUSE_TLS -o generic-morest= ack-thread.o -MT generic-morestack-thread.o -MD -MP -MF generic-morestack-t= hread.dep -c ../../../libgcc/generic-morestack-thread.c=20 ../../../libgcc/generic-morestack-thread.c:41:21: fatal error: pthread.h: N= o such file or directory compilation terminated. make[3]: *** [../../../libgcc/static-object.mk:17: generic-morestack-thread= .o] Error 1 Thanks a lot for listening! Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com