From: Matias Garcia <mgarcia@rossvideo.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to tune powerpc e500v2 cpus in BR
Date: Mon, 27 Jun 2011 16:23:55 -0400 [thread overview]
Message-ID: <4E08E6DB.4070606@rossvideo.com> (raw)
In-Reply-To: <BANLkTinSC4W8=vwRCHYmBndbJqt7rv=xgQ@mail.gmail.com>
On 11-06-27 04:10 PM, raymond zhao wrote:
> On Sun, Jun 26, 2011 at 11:59 PM, Baruch Siach<baruch@tkos.co.il> wrote:
>> Hi Raymond, Matias,
>> I'm also using the CodeSourcery toolchain for the e500v2 target (P1011), and I
>> figured out that I must pass -te500v2 to gcc at link time as well. Since there
>> is no generic way to add LDFLAGS options in Buildroot, I've posted the patch
>> at http://lists.busybox.net/pipermail/buildroot/2011-June/043668.html. Did you
>> find a better solution?
>>
>> baruch
> Hi, Baruch
> I took a look at the CodeSourcery. Looks it doesn't support uCLibc.
> Best regards,
> changbing
changbing: That's correct. You may find an older toolchain from them
that uses uClibc, but you'll have to specify it yourself in the
Buildroot config. I found a very small difference in size (<2MB) between
uclibc and eglibc filesystems, but I'm using 32MB of flash just for the
OS, so small is relative.
Baruch: I use the external toolchain wrapper introduced just before
2011.05, but I had to patch it to add arbitrary options. I posted a
couple of patches here, one that introduces a new option for selecting
the sysroot when compiling the external wrapper, and another that simply
passes the BR2_TARGET_OPTIMIZATIONS to the external wrapper, but they
didn't get much attention.
I prefer the first method (new config option) because you can choose not
to pass the optimizations@some later point for whatever reason, and
thus use the wrapper only to select your sysroot.
Cheers,
Matias
next prev parent reply other threads:[~2011-06-27 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 14:27 [Buildroot] how to tune powerpc e500v2 cpus in BR raymond zhao
2011-06-24 17:31 ` Matias Garcia
2011-06-24 21:14 ` raymond zhao
2011-06-24 21:41 ` raymond zhao
2011-06-24 21:44 ` Bryan Hundven
2011-06-24 22:04 ` raymond zhao
2011-06-24 22:07 ` Bryan Hundven
2011-06-27 3:59 ` Baruch Siach
2011-06-27 20:10 ` raymond zhao
2011-06-27 20:23 ` Matias Garcia [this message]
2011-06-28 4:23 ` Baruch Siach
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=4E08E6DB.4070606@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 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.