From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] elf2flt .ARM.exidx and .ARM.extab section handling
Date: Fri, 28 Aug 2015 15:35:06 +0200 [thread overview]
Message-ID: <20150828153506.3567c225@free-electrons.com> (raw)
In-Reply-To: <180102384.TlRWI16dqe@raillard-dv6>
Dear Douglas RAILLARD,
On Fri, 28 Aug 2015 15:15:34 +0200, Douglas RAILLARD wrote:
> > Also, can you ask on the nommu.org mailing list
> > (http://lists.nommu.org/listinfo/nommu) is they have a new official
> > upstream location for elf2flt ?
>
> Sure
In the mean time, Waldemar pointed to his own Git tree of elf2flt.
Still, it would be great to have some kind of "official" upstream place
for elf2flt development.
> I'll study these sources, as they should handle correctly the .ARM.exidx and
> .ARM.extab sections, thanks for the pointer.
> Caveat: From https://github.com/jserv/stm32f429-linux-builder:
> SourceryG++ arm-2011.03 is known to NOT work (but elf2flt is probably still
> useable).
You can find all other versions, including sources, at
http://sourcery.mentor.com/public/gnu_toolchain/.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-28 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 19:11 [Buildroot] elf2flt .ARM.exidx and .ARM.extab section handling Douglas RAILLARD
2015-08-28 9:53 ` Thomas Petazzoni
2015-08-28 13:15 ` Douglas RAILLARD
2015-08-28 13:35 ` Thomas Petazzoni [this message]
2015-08-28 15:02 ` Waldemar Brodkorb
2015-08-28 15:27 ` Douglas RAILLARD
2015-08-28 16:45 ` Thomas Petazzoni
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=20150828153506.3567c225@free-electrons.com \
--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