From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6572] New: [PowerPC] Buildroot uses wrong external toolchain libraries for non-generic architecture variants
Date: Mon, 21 Oct 2013 06:20:40 +0000 (UTC) [thread overview]
Message-ID: <bug-6572-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6572
Summary: [PowerPC] Buildroot uses wrong external toolchain
libraries for non-generic architecture variants
Product: buildroot
Version: 2013.08
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: aleek998 at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Using Codesoucery external toolchain, and architecture variant 8548 / e500v2,
toolchain libraries are copied from powerpc-linux-gnu/libc/nof but should be
copied from powerpc-linux-gnu/libc/te500v2.
Library powerpc-linux-gnu/libc/nof/usr/lib/libstdc++.so contains 'lwsync'
instruction which is invalid on e500v2 and causes Invalid Instruction fault for
every c++ based application.
I tested the temporaty workaround (copying te500v2 dir to nof dir) and it
solved the bug.
I suppose that this bug might involve all PowerPC architecture variants.
--
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:[~2013-10-21 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 6:20 bugzilla at busybox.net [this message]
2013-10-21 6:33 ` [Buildroot] [Bug 6572] [PowerPC] Buildroot uses wrong external toolchain libraries for non-generic architecture variants 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-6572-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.