From: James Newell <jnewell@wgate.com>
To: buildroot@busybox.net
Subject: [Buildroot] building ARM toolchain with nofpu
Date: Wed, 07 Feb 2007 15:09:50 -0500 [thread overview]
Message-ID: <1170878990.10007.4.camel@ndragon.eng.wgate.com> (raw)
In-Reply-To: <200702012015.55089.yann.morin.1998@anciens.enib.fr>
Has any one had any progress with building uclibc default soft float
using gcc 4.1.1?
Thanks,
Jim
On Thu, 2007-02-01 at 20:15 +0100, Yann E. MORIN wrote:
> Hello all!
> Michel, Carl.
>
> On Thursday 01 February 2007 010, Michel Benoit wrote:
> > I'm trying to build a toolchain with soft floating point enabled for
> > ARM arm26t target platform. I'm doing this in order to build u-boot
> > for my target.
> [--SNIP--]
> > The build stops due to missing symbols while linking uclibc:
> >
> > make[1]: Entering directory
> > `/home/michel/Projects/sepab/exyplus/sw/bsp/build/buildroot/toolchain_build_arm_nofpu/uClibc'
> > LD libuClibc-0.9.29.so
> > 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+0xd4): undefined reference to `__nedf2'
> > _fpmaxtostr.c:(.text+0xf8): undefined reference to `__eqdf2'
> > _fpmaxtostr.c:(.text+0x114): undefined reference to `__divdf3'
> > _fpmaxtostr.c:(.text+0x120): undefined reference to `__ltdf2'
> > _fpmaxtostr.c:(.text+0x1c4): undefined reference to `__muldf3'
> > _fpmaxtostr.c:(.text+0x388): undefined reference to `__gedf2'
> > _fpmaxtostr.c:(.text+0x430): undefined reference to `__adddf3'
> > libc/libc_so.a(__psfs_do_numeric.os): In function `__psfs_do_numeric':
> > __psfs_do_numeric.c:(.text+0x520): undefined reference to `__truncdfsf2'
> > libc/libc_so.a(strtof.os): In function `strtof':
> > strtof.c:(.text+0x1c): undefined reference to `__extendsfdf2'
> > /home/michel/Projects/sepab/exyplus/sw/bsp/build/buildroot/build_arm_nofpu/staging_dir/lib/gcc/arm-linux-uclibc/4.1.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
> > make[1]: Leaving directory
> > `/home/michel/Projects/sepab/exyplus/sw/bsp/build/buildroot/toolchain_build_arm_nofpu/uClibc'
> > make: *** [/home/michel/Projects/sepab/exyplus/sw/bsp/build/buildroot/toolchain_build_arm_nofpu/uClibc/lib/libc.a]
> > Error 2
>
> I'm tracking this down right now, and I've found that those functions are not
> included in libgcc.a because gcc-4.1.1/gcc/config.gcc does not validate
> arm/t-arm-elf for arm*-linux* targets, but arm/t-arm, which does not describe
> those functions as to be included in libgcc.a.
>
> I've tried a quick fix (replacing t-arm with t-arm-elf), but it still does
> not work. I haven't had time right to investigate more. Later tongiht.
>
> > Are there any other config options that need to be selected/unselected
> > in order to get this to work?
>
> You could try with a known working gcc (gcc-3.4.4 is working real fine here),
> unless you really can't for very good reasons, but compiling u-boot should
> Just Work (TM).
>
> Regards,
> Yann E. MORIN.
>
next prev parent reply other threads:[~2007-02-07 20:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 0:09 [Buildroot] building ARM toolchain with nofpu Michel Benoit
2007-02-01 19:15 ` Yann E. MORIN
2007-02-01 20:51 ` Michel Benoit
2007-02-01 22:46 ` Ulf Samuelsson
2007-02-05 9:26 ` Michel Benoit
2007-02-07 20:09 ` James Newell [this message]
2007-02-07 20:24 ` Yann E. MORIN
2007-02-07 20:36 ` Yann E. MORIN
2007-02-08 7:50 ` carl zhu
2007-02-08 14:26 ` James Newell
2007-02-09 1:41 ` James Newell
2007-02-09 13:10 ` Bernhard Fischer
2007-03-01 10:01 ` carl zhu
2007-02-08 17:25 ` Bernhard Fischer
2007-02-08 17:33 ` Yann E. MORIN
2007-02-08 17:40 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 14:10 James Newell
2007-02-09 14:29 ` Bernhard Fischer
2007-02-09 17:57 ` Yann E. MORIN
2007-02-09 18:21 ` Bernhard Fischer
2007-02-09 18:48 ` Yann E. MORIN
2007-02-09 14:51 James Newell
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=1170878990.10007.4.camel@ndragon.eng.wgate.com \
--to=jnewell@wgate.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