From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1225] New: Buildroot fails to account for "nof" subdirectory (no floating point)
Date: Tue, 2 Mar 2010 20:25:47 +0000 (UTC) [thread overview]
Message-ID: <bug-1225-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1225
Summary: Buildroot fails to account for "nof" subdirectory (no
floating point)
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gnemesure at avtec.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I am using buildroot-2010.2 to target a 440GP processor with no hardware
floating point.
When software floating point is enabled (BR2_SOFT_FLOAT), the gcc build puts
libgcc_s.so, libstdc++.so, etc. in an "nof" subdirectory that buildroot is not
accommodating. These are deposited in
$(STAGING_DIR)/usr/powerpc-linux-uclibc/lib/nof
but the toolchain/gcc/gcc-uclibc-4.x.mk makefile tries to copy these files from
$(STAGING_DIR)/usr/powerpc-linux-uclibc/lib
which results in failure to copy the libraries to the target filesystem.
This is with GCC 4.3.4. I'm not sure if this applies to other versions as well.
As a workaround, I think I can enable floating point in the kernel, and then
enable hardware floating point in the toolchain.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-03-02 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 20:25 bugzilla at busybox.net [this message]
2010-03-02 21:50 ` [Buildroot] [Bug 1225] Buildroot fails to account for "nof" subdirectory (no floating point) bugzilla at busybox.net
2010-03-03 15:05 ` bugzilla at busybox.net
2010-03-03 15:11 ` bugzilla at busybox.net
2010-03-03 16:06 ` bugzilla at busybox.net
2010-03-03 23:15 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-29 19:27 ` bugzilla at busybox.net
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=bug-1225-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.