unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "U.Mutlu" <um@mutluit.com>
Cc: gcc-help@gcc.gnu.org, guix-devel@gnu.org
Subject: SOLVED: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Wed, 11 Jul 2018 19:01:54 +0200	[thread overview]
Message-ID: <87pnztln99.fsf_-_@gnu.org> (raw)
In-Reply-To: <5B452C86.6090003@mutluit.com> (U. Mutlu's message of "Wed, 11	Jul 2018 00:00:38 +0200")

U.Mutlu writes:

> Just a tip: you can build the compiler much faster if you use --disable-bootstrap
> (here it reduces the compile time from 111 minutes down to 12 minutes).
> After it's ok, then you can build w/o it to also test the
> bootstrapping.

Thanks!  I'm very grateful for your help.  I succeeded in building
gcc-4.7.4 from almost no binary seeds[0] for GuixSD!

The weird error in Subject was caused by configure+make (and my usage of
configure flags, environment settings) trying to use CC_FOR_BUILD (the
i368-unknow-linux-gcc 2.95.3 compiler) to build libgcc2.c

Here's the configure that I used, which works.

../build/configure\
 --build=i686-unknown-linux-gnu\
 --host=i686-unknown-linux-gnu\
 --with-native-system-header-dir=/gnu/store/lwadx3lm73f8rmy8cvwijrflb9wgcm7j-glibc-mesboot-2.2.5/include\
 --with-build-sysroot=/gnu/store/lwadx3lm73f8rmy8cvwijrflb9wgcm7j-glibc-mesboot-2.2.5/include\
 --prefix=/gnu/store/bci6j4dfrmkfzqbpbbcz5ypk8xmr0j5z-gcc-mesboot-4.7.4\
 --disable-bootstrap\
 --disable-decimal-float\
 --disable-libatomic\
 --disable-libcilkrts\
 --disable-libgomp\
 --disable-libitm\
 --disable-libmudflap\
 --disable-libquadmath\
 --disable-libsanitizer\
 --disable-libssp\
 --disable-libvtv\
 --disable-lto\
 --disable-lto-plugin\
 --disable-multilib\
 --disable-plugin\
 --disable-shared\
 --disable-threads\
 --enable-languages=c\
 --enable-static\
 --enable-threads=single\
 --disable-libstdc__-v3\
 --disable-libstdcxx-pch\
 --disable-build-with-cxx

Greetings,
janneke

[0] http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/mes.scm?h=wip-bootstrap

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  parent reply	other threads:[~2018-07-11 17:01 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
2018-07-10 20:19             ` Jonathan Wakely
     [not found]             ` <5B452C86.6090003@mutluit.com>
2018-07-11 17:01               ` Jan Nieuwenhuizen [this message]
2018-07-11 18:06                 ` SOLVED: " 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=87pnztln99.fsf_-_@gnu.org \
    --to=janneke@gnu.org \
    --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).