From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "U.Mutlu" <um@mutluit.com>
Cc: gcc-help@gcc.gnu.org, guix-devel@gnu.org
Subject: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Tue, 10 Jul 2018 17:02:52 +0200 [thread overview]
Message-ID: <87wou3m8v7.fsf@gnu.org> (raw)
In-Reply-To: <5B442D84.8030805@mutluit.com> (U. Mutlu's message of "Tue, 10 Jul 2018 05:52:36 +0200")
U.Mutlu writes:
> You have attached config.h of 2 targets.
> Is just one of them failing, or both?
I hoped to just get one, but I get two; I configure using
../build/configure --host=i386-unknown-linux --target=i386-unknown-linux ...
> And of course: are they both using the same target arch, just
> differing in 64bit/32bit?
Not even, this is inside a 32bit VM. I was hoping to build an x86
toolchain on x86_64, but after these problems I setup a 32bit VM
Maybe I should use
--host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
?
> The difference in them is:
> diff /tmp/build-i686-pc-linux-gnu--libiberty--config.h
> /tmp/host-i386-unknown-linux--libiberty--config.h | less -Sn
> 171c171
> < #define HAVE_MMAP 1
> ---
>> /* #undef HAVE_MMAP */
> 444c444
> < #define STACK_DIRECTION -1
> ---
>> #define STACK_DIRECTION 0
>
> If they both are the same arch then I would suggest to get the one
> fixed first where the STACK_DIRECTION is seemingly detected wrongly.
Hmm, this is definitely wrong.
I'll have a look at this first...
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-07-10 15:02 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 ` SOLVED: " Jan Nieuwenhuizen
2018-07-11 18:06 ` U.Mutlu
2018-07-11 19:23 ` Jan Nieuwenhuizen
2018-07-10 15:02 ` Jan Nieuwenhuizen [this message]
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=87wou3m8v7.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).