unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: um@mutluit.com, gcc-help@gcc.gnu.org, Guix-devel <guix-devel@gnu.org>
Subject: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Tue, 10 Jul 2018 21:51:15 +0200	[thread overview]
Message-ID: <87601mna30.fsf@gnu.org> (raw)
In-Reply-To: <87sh4rm8nb.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 10	Jul 2018 17:07:36 +0200")

Jan Nieuwenhuizen writes:

> Gábor 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?  
>
> Ah!  That makes me even more supicious... I was wondering about this
> command
>
>     i386-unknown-linux-gcc ... -DIN_GCC -o _muldi3.o -c ../.././libgcc/libgcc2.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=i686-unknown-linux-gnu
    --host=i686-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=c
    --enable-static
    --prefix=/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4
    --with-build-sysroot=/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqdx5vfly-glibc-mesboot-2.2.5/include
    --with-native-system-header-dir=/gnu/store/ffj8vq5zvm26jhw26fcmz3bjqdx5vfly-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/tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/bin/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/lib/ -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/include -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/sys-include --sysroot=/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  -isystem ./include   -fpic -g -DIN_LIBGCC2 -fno-stack-protector   -fpic -I. -I. -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc -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 

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/tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4/build/./gcc/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/bin/ -B/gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/lib/ -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/include -isystem /gnu/store/mkhbgqfpj17p2pfpza95y56dlw2fmfj4-gcc-mesboot-4.7.4/i686-unknown-linux-gnu/sys-include --sysroot=/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  -isystem ./include   -fpic -g -DIN_LIBGCC2 -fno-stack-protector   -fpic -I. -I. -I../.././gcc -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc -I../../../libgcc/../include  -DHAVE_CC_TLS  -DUSE_TLS -o generic-morestack-thread.o -MT generic-morestack-thread.o -MD -MP -MF generic-morestack-thread.dep  -c ../../../libgcc/generic-morestack-thread.c 
../../../libgcc/generic-morestack-thread.c:41:21: fatal error: pthread.h: No 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
-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  reply	other threads:[~2018-07-10 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 16:57 gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF' Jan Nieuwenhuizen
2018-07-09 18:28 ` U.Mutlu
2018-07-09 19:40   ` Jan Nieuwenhuizen
2018-07-10  3:52     ` U.Mutlu
2018-07-10  7:31       ` Gábor Boskovits
2018-07-10 15:07         ` Jan Nieuwenhuizen
2018-07-10 19:51           ` Jan Nieuwenhuizen [this message]
2018-07-10 20:19             ` Jonathan Wakely
     [not found]             ` <5B452C86.6090003@mutluit.com>
2018-07-11 17:01               ` SOLVED: " Jan Nieuwenhuizen
2018-07-11 18:06                 ` U.Mutlu
2018-07-11 19:23                   ` Jan Nieuwenhuizen
2018-07-10 15:02       ` Jan Nieuwenhuizen
2018-07-10 15:54 ` Danny Milosavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87601mna30.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=boskovits@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=um@mutluit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).