unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: um@mutluit.com
Cc: 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 09:31:53 +0200	[thread overview]
Message-ID: <CAE4v=piZcS7d5=wu8j0i-yhdd+9go6bLo3pg-wN7WWXon2KhMA@mail.gmail.com> (raw)
In-Reply-To: <5B442D84.8030805@mutluit.com>

[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]

U.Mutlu <um@mutluit.com> ezt írta (időpont: 2018. júl. 10., K, 5:53):

> Jan Nieuwenhuizen wrote on 07/09/2018 09:40 PM:
> > U.Mutlu writes:
> >
> >> What do you get if you grep for "error: " in the xxx/libgcc/config.log
> >> under the builddir?
> >
> > janneke@guix-x86 /tmp/guix-build-gcc-mesboot-4.7.4.drv-0/gcc-4.7.4$
> grep 'error: ' i386-unknown-linux/libgcc/config.log
> > conftest.c:9:28: error: ac_nonexistent.h: No such file or directory
> > conftest.c:13: error: size of array 'test_array' is negative
> > conftest.c:13: error: size of array 'test_array' is negative
> > conftest.c:13: error: size of array 'test_array' is negative
> > conftest.c:13: error: size of array 'test_array' is negative
> > conftest.c:14: error: size of array 'test_array' is negative
> > conftest.c:14: error: size of array 'test_array' is negative
> > conftest.c:14: error: size of array 'test_array' is negative
> > conftest.c:14: error: size of array 'test_array' is negative
> > conftest.c:14: error: size of array 'test_array' is negative
> > conftest.c:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'x'
> > conftest.c:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before '_Fract'
> >
> >> It would also be helpful if you could post also your libiberty/config.h
> >
> > Sure, attached.
> >
> > janneke
>
>
> You have attached config.h of 2 targets.
> Is just one of them failing, or both?
> And of course: are they both using the same target arch, just differing in
> 64bit/32bit?
>
> 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.
>
>
> And don't use -Werror when compiling, ie. don't treat warnings as error.
>
>
> And try to find out the reason for the above configure-error:
>
>  > conftest.c:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before 'x'
>  > conftest.c:11: error: expected '=', ',', ';', 'asm' or '__attribute__'
> before '_Fract'
>
>
> I forgot to ask: please post also the "error: "'s in libiberty/config.log,
> ie.
> the grep-output like above.
>
>
>
>
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?

[-- Attachment #2: Type: text/html, Size: 3536 bytes --]

  reply	other threads:[~2018-07-10  7:32 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 [this message]
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
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='CAE4v=piZcS7d5=wu8j0i-yhdd+9go6bLo3pg-wN7WWXon2KhMA@mail.gmail.com' \
    --to=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).