From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] build root error with nofpu
Date: Fri, 19 Jan 2007 15:41:17 +0100 [thread overview]
Message-ID: <20070119144117.GA16604@aon.at> (raw)
In-Reply-To: <02f701c73b97$144f4bb0$0c96a8c0@Thomas>
On Fri, Jan 19, 2007 at 02:57:20PM +0800, thomas.luo wrote:
>>>do a rm -rf build_arm_nofpu/* toolchain_build_arm_nofpu/*
>>>then make sure that your BR2_JLEVEL=1 and invoke "make" again and paste
>>>the first error you get.
>>>
>>>Providing your .config and the uclibc.config would help, too.
>>
>>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+0x51c): undefined reference to `__truncdfsf2'
>>libc/libc_so.a(strtof.os): In function `strtof':
>>strtof.c:(.text+0x1c): undefined reference to `__extendsfdf2'
>>/mnt/rootbb/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] ??? 2
>>make[1]: Leaving directory
>>`/mnt/rootbb/buildroot/toolchain_build_arm_nofpu/uClibc'
>>make: ***
>>[/mnt/rootbb/buildroot/toolchain_build_arm_nofpu/uClibc/lib/libc.a] ??? 2
>>[root at localhost buildroot]#
>>
[snip inlined buildroot.config]
Looks like you did not send your uClibc.config?
Please attach them both, non-inlined, so i can save them away easily and
try to reproduce that problem.
thanks,
next prev parent reply other threads:[~2007-01-19 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 6:57 [Buildroot] build root error with nofpu thomas.luo
2007-01-19 14:41 ` Bernhard Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-17 1:03 thomas.luo
2007-01-17 18:18 ` Bernhard Fischer
2007-01-19 6:56 ` thomas.luo
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=20070119144117.GA16604@aon.at \
--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