From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for armeb, gcc-4.2.1 fails to build
Date: Tue, 16 Oct 2007 15:56:38 +1000 [thread overview]
Message-ID: <20071016055638.GA23927@cloud.net.au> (raw)
In-Reply-To: <20071016034233.GA21412@cloud.net.au>
On Tue, Oct 16, 2007 at 01:42:33PM +1000, Hamish Moffatt wrote:
> So now it just fails like this:
>
> > libc/libc_so.a(difftime.os): In function `difftime':
> > difftime.c:(.text+0x8): undefined reference to `__floatsidf'
> > difftime.c:(.text+0x2c): undefined reference to `__subdf3'
> > libc/libc_so.a(_fpmaxtostr.os): In function `_fpmaxtostr':
> > _fpmaxtostr.c:(.text+0xe0): undefined reference to `__nedf2'
> > _fpmaxtostr.c:(.text+0x104): undefined reference to `__eqdf2'
> > _fpmaxtostr.c:(.text+0x120): undefined reference to `__divdf3'
> > _fpmaxtostr.c:(.text+0x12c): undefined reference to `__ltdf2'
> > _fpmaxtostr.c:(.text+0x1e0): undefined reference to `__muldf3'
> > _fpmaxtostr.c:(.text+0x39c): undefined reference to `__gedf2'
> > _fpmaxtostr.c:(.text+0x42c): undefined reference to `__floatunsidf'
> > libc/libc_so.a(__psfs_do_numeric.os): In function `__psfs_do_numeric':
> > __psfs_do_numeric.c:(.text+0x54c): undefined reference to `__truncdfsf2'
> > libc/libc_so.a(strtof.os): In function `strtof':
> > strtof.c:(.text+0x1c): undefined reference to `__extendsfdf2'
> > libc/libc_so.a(__strtofpmax.os): In function `__strtofpmax':
> > __strtofpmax.c:(.text+0x154): undefined reference to `__adddf3'
> > /home/hamish/tmp/br/buildroot/build_armeb/staging_dir/usr/lib/gcc/armeb-linux-uclibc/4.2.1/libgcc.a(_fixunsdfsi.o): In function `__fixunsdfsi':
> > libgcc2.c:(.text+0x34): undefined reference to `__fixdfsi'
> > make[2]: *** [lib/libc.so] Error 1
> > make[1]: *** [lib/libc.so.0] Error 2
And this is caused by soft-float.
Summary of situation:
arm EABI hard-float: builds.
armeb EABI hard-float: libgcc_s.so fails to link due to incorrect file
format of libc.so
arm/armeb OABI hard-float: builds.
arm/armeb OABI soft-float: fails as above (both endians fail the same
way).
I haven't tried soft-float EABI.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2007-10-16 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 5:48 [Buildroot] buildroot for armeb, gcc-4.2.1 fails to build Hamish Moffatt
2007-10-15 15:06 ` Jonathan Nalley
2007-10-15 20:48 ` Ulf Samuelsson
2007-10-16 0:16 ` Hamish Moffatt
2007-10-16 3:42 ` Hamish Moffatt
2007-10-16 5:56 ` Hamish Moffatt [this message]
2007-10-16 6:00 ` Ulf Samuelsson
2007-10-16 6:44 ` Hamish Moffatt
2007-10-17 1:19 ` [Buildroot] PATCH: " Hamish Moffatt
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=20071016055638.GA23927@cloud.net.au \
--to=hamish@cloud.net.au \
--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