From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc: 4.3.1
Date: Sat, 21 Jun 2008 14:21:25 +0200 [thread overview]
Message-ID: <20080621122124.GZ10734@mx.loc> (raw)
In-Reply-To: <200806202050.32567.fboudra@gmail.com>
On Fri, Jun 20, 2008 at 08:50:31PM +0200, Fathi Boudra wrote:
>On Friday 20 June 2008 20:32:07 Peter Korsgaard wrote:
>
>> I also seem to have problems on powerpc, but haven't looked at it yet
>> in detail:
>>
>> /home/peko/source/buildroot/toolchain_build_powerpc/gcc-4.3.1/libgcc/../lib
>>decnumber/decExcept.c:30:18: error: fenv.h: No such file or directory
>> make[2]: *** [decExcept.o] Error 1
>> make[2]: Leaving directory
>> `/home/peko/source/buildroot/toolchain_build_powerpc/gcc-4.3.1-initial/powe
>>rpc-linux-uclibc/libgcc' make[1]: *** [all-target-libgcc] Error 2
>> make[1]: Leaving directory
>> `/home/peko/source/buildroot/toolchain_build_powerpc/gcc-4.3.1-initial'
>
>That's it. I retried right now and got same issue with a defconfig (except
>arch + gcc switch):
>
>ld_powerpc/gcc-4.3.1/libgcc -I/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/. -I/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../gcc -I/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../include -I/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../libdecnumber/dpd -I/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../libdecnumber -I../../libdecnumber -DHAVE_CC_TLS -o
>decExcept.o-MT decExcept.o -MD -MP -MF
>decExcept.dep -c /buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../libdecnumber/decExcept.c
>/buildd/build-area/toolchain/buildroot-chrp32/toolchain_build_powerpc/gcc-4.3.1/libgcc/../libdecnumber/decExcept.c:30:18:
>error: fenv.h: No such file or directory
so why don't you just disable it?
I've only added fexcept*() for my personal use on i386, no other arch
has it, currently. This is expected behaviour.
next prev parent reply other threads:[~2008-06-21 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 19:06 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc: 4.3.1 jacmet at uclibc.org
2008-06-20 15:50 ` Fathi Boudra
2008-06-20 15:56 ` Bernhard Fischer
2008-06-20 16:06 ` Fathi Boudra
2008-06-20 16:40 ` Bernhard Fischer
2008-06-20 18:32 ` Peter Korsgaard
2008-06-20 18:50 ` Fathi Boudra
2008-06-20 20:13 ` Fathi Boudra
2008-06-21 12:51 ` Bernhard Fischer
2008-06-25 19:22 ` Fathi Boudra
2008-06-21 12:21 ` Bernhard Fischer [this message]
2008-06-20 18:24 ` Peter Korsgaard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080621122124.GZ10734@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox