From mboxrd@z Thu Jan  1 00:00:00 1970
From: "U.Mutlu" <um@mutluit.com>
Subject: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Tue, 10 Jul 2018 05:52:36 +0200
Message-ID: <5B442D84.8030805@mutluit.com>
References: <87sh4sny8j.fsf@gnu.org> <5B43A955.7090904@mutluit.com> <87muv0nqoi.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <gcc-help-return-62169-gcc-help=m.gmane.org@gcc.gnu.org>
List-Unsubscribe: <mailto:gcc-help-unsubscribe-gcc-help=m.gmane.org@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
In-Reply-To: <87muv0nqoi.fsf@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: gcc-help@gcc.gnu.org, guix-devel@gnu.org
List-Id: guix-devel.gnu.org

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.