From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] buildroot: target: Add Blackfin architecture support.
Date: Tue, 26 Mar 2013 09:41:02 +0100 [thread overview]
Message-ID: <20130326094102.094def3d@skate> (raw)
In-Reply-To: <CAJxxZ0OOj=vi5xuCp79vU0_kX_KNx+UX+CSRkLkr4_xsfNtS2Q@mail.gmail.com>
Dear Sonic Zhang,
On Tue, 26 Mar 2013 16:16:07 +0800, Sonic Zhang wrote:
> > If you need to have different prefixes, isn't it possible to hook into one
> > of these variables, instead of creating a new variable
> > CROSS_COMPILE_SHARED_ELF/FLAT ?
> > Depending on the elf/flat choice, you would then for example set
> > BR2_TOOLCHAIN_EXTERNAL_PREFIX (possible from kconfig directly) (but this
> > would work only for external toolchains), or override TARGET_CROSS.
> > With such a change, you can reuse TARGET_CC and TARGET_READELF.
>
> I do set BR2_TOOLCHAIN_EXTERNAL_PREFIX to bfin-uclinux via kconfig to
> build the complete packages in buildroot. Meanwhile, I would like to
> install FDPIC libraries as well from the bfin-linux-uclibc toolchain
> folder, which is different from the bfin-uclinux I set to
> BR2_TOOLCHAIN_EXTERNAL_PREFIX.
>
> Blackfin toolchain bfin-linux-uclibc and bfin-uclinux are located in
> different path.
But the current external toolchain logic in
toolchain/toolchain-external/ext-tool.mk only extracts either the
bfin-uclinux sysroot *or* the bfin-linux-uclibc sysroot, so you in
practice don't have both at the same time, at least with the current
Buildroot. So presumably this would also need to be changed, right?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-26 8:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 9:01 [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Sonic Zhang
2013-03-22 9:01 ` [Buildroot] [PATCH v3 2/2] buildroot: target: Add Blackfin architecture support Sonic Zhang
2013-03-22 14:54 ` Thomas Petazzoni
2013-03-25 11:33 ` Sonic Zhang
2013-03-25 11:47 ` Thomas De Schampheleire
2013-03-26 8:16 ` Sonic Zhang
2013-03-26 8:41 ` Thomas Petazzoni [this message]
2013-03-26 9:36 ` Sonic Zhang
2013-03-26 10:08 ` Thomas Petazzoni
2013-03-26 7:25 ` Arnout Vandecappelle
2013-03-26 8:15 ` Thomas Petazzoni
2013-03-28 8:20 ` Sonic Zhang
2013-03-28 8:56 ` Thomas Petazzoni
2013-03-29 9:50 ` Sonic Zhang
2013-03-22 14:29 ` [Buildroot] [PATCH v3 1/2] package: Makefile.in: Add target compilation flags for NOMMU architecture Thomas Petazzoni
2013-03-22 17:28 ` Thomas De Schampheleire
2013-03-25 7:11 ` Arnout Vandecappelle
2013-03-25 7:50 ` Sonic Zhang
2013-03-25 7:57 ` Sonic Zhang
2013-03-25 7:58 ` Thomas Petazzoni
2013-03-25 8:51 ` Sonic Zhang
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=20130326094102.094def3d@skate \
--to=thomas.petazzoni@free-electrons.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