From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sh: Fix Buildroot sh targets to match gnuconfig targets
Date: Tue, 10 May 2011 10:20:47 +0200 [thread overview]
Message-ID: <20110510102047.1fffa641@surf> (raw)
In-Reply-To: <201105101001.31879.yann.morin.1998@anciens.enib.fr>
On Tue, 10 May 2011 10:01:31 +0200
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> wrote:
> On Tuesday 10 May 2011 084704 Thomas Petazzoni wrote:
> > Just curious, as I have never used Buildroot to build a toolchain for
> > non-MMU platforms (only used pre-built Blackfin toolchains so far). How
> > does this elf2flt thing fits into the toolchain build process ?
>
> elf2flt provides its own linker to replace ld when the output is the flat
> ELF format. When installing, elf2flt renames the original ld coming from
> the binutils, installs its own ld.elf2flt linker and a ld wrapper that
> checks the arguments. If the format is flat ELF, then the wrapper calls to
> the ld.elf2flt linker; otherwise, it calls to the original linker.
>
> So one first installs binutils as usual, and then install elf2flt.
Thanks Yann for these details. I'm wondering if this actually works
fine in Buildroot or not.
Do you know if elf2flt has a well-known upstream location, so that we
can use it instead of having the source code inside the BR tree?
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:[~2011-05-10 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 13:12 [Buildroot] [PATCH] sh: Fix Buildroot sh targets to match gnuconfig targets Phil Edworthy
2011-05-10 6:47 ` Thomas Petazzoni
2011-05-10 7:34 ` PHIL.EDWORTHY at renesas.com
2011-05-10 7:48 ` Thomas Petazzoni
2011-05-10 8:01 ` Yann E. MORIN
2011-05-10 8:20 ` Thomas Petazzoni [this message]
2011-05-10 8:35 ` Yann E. MORIN
2011-07-18 21:26 ` Peter Korsgaard
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=20110510102047.1fffa641@surf \
--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 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.