From: Matias Garcia <mgarcia@rossvideo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Codesourcery multi-lib selection in buildroot
Date: Wed, 04 May 2011 16:52:08 -0400 [thread overview]
Message-ID: <4DC1BC78.4050103@rossvideo.com> (raw)
I'm building an OS for a PowerPC e500v2 core. Originally, I used a stock
buildroot toolchain (uclibc), but was not able to optimize a
time-critical section of our application. With the CodeSourcery
compiler, I am. Unfortunately, even setting -te500v2 in the buildroot
optimizations (and hacking it into the TARGET_LDFLAGS) doesn't fix all
cases. Certain packages within buildroot seem to link against the wrong
library (linker complains that one library is compiled with hard-float
and another with soft-float, etc). Is there a way to tell buildroot (or
Make in general) to always link against a certain library set?
Cheers,
Matias
--
*Matias Garcia*
/Embedded Software Developer/
Ross Video | Live Production Technology
www.rossvideo.com <http://www.rossvideo.com>
+1 (613) 228 1198 x4264
next reply other threads:[~2011-05-04 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 20:52 Matias Garcia [this message]
2011-05-05 19:10 ` [Buildroot] Codesourcery multi-lib selection in buildroot Thomas Petazzoni
2011-05-06 18:38 ` Matias Garcia
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=4DC1BC78.4050103@rossvideo.com \
--to=mgarcia@rossvideo.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