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 17:02:52 +0200 Message-ID: <87wou3m8v7.fsf@gnu.org> References: <87sh4sny8j.fsf@gnu.org> <5B43A955.7090904@mutluit.com> <87muv0nqoi.fsf@gnu.org> <5B442D84.8030805@mutluit.com> 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: <5B442D84.8030805@mutluit.com> (U. Mutlu's message of "Tue, 10 Jul 2018 05:52:36 +0200") To: "U.Mutlu" Cc: gcc-help@gcc.gnu.org, guix-devel@gnu.org List-Id: guix-devel.gnu.org 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=3Di386-unknown-linux --target=3Di386-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=3Di686-pc-linux-gnu --target=3Di686-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 --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com