From: Douglas RAILLARD <public.douglas.raillard@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] elf2flt .ARM.exidx and .ARM.extab section handling
Date: Fri, 28 Aug 2015 15:15:34 +0200 [thread overview]
Message-ID: <180102384.TlRWI16dqe@raillard-dv6> (raw)
In-Reply-To: <20150828115314.606c5049@free-electrons.com>
Thomas
On Friday 28 August 2015 11:53:14, Thomas Petazzoni wrote:
> > Now elf2flt sources had been moved out of the buildroot tree, but the
> > currently used upstream has no obvious mean of contact so here is a serie
> > of small patches that allow the elf2flt toolchain to compile cleanly C
> > code (C++ not tested).
> Can you submit this as proper patches against Buildroot, i.e a patch
> adding patches in package/elf2flt/ ?
Sure, I'll patch my patch to create a patch adding patches right away.
> 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
> > Here is the URL of that prebuilt toolchain:
> > https://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/ar
> > m-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
> Are you sure? This is a Linux toolchain, not a uClinux toolchain.
Well, it runs on linux host and output working bFLT binaries (runtime tested)
for a uClinux target. Not a lot of people seems to be working with uClinux,
but I found that this toolchain was the one used by most of people working
with the stm32f429-discovery board, probably because Emcraft Systems has
released a BSP for that board and they point to (nearly) that toolchain.
(http://www.emcraft.com/stm32f429discovery#release-materials).
> If you want the sources of:
>
>
> http://sourcery.mentor.com/public/gnu_toolchain/arm-uclinuxeabi/arm-2011.03
> -46-arm-uclinuxeabi-i686-pc-linux-gnu.tar.bz2
>
> they are available at:
>
>
> http://sourcery.mentor.com/public/gnu_toolchain/arm-uclinuxeabi/arm-2011.03
> -46-arm-uclinuxeabi.src.tar.bz2
>
> And this one does have the sources of elf2flt:
>
> arm-2011.03-46-arm-uclinuxeabi/elf2flt-2011.03-46.tar.bz2
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).
Best regards,
Douglas
--
Douglas RAILLARD
next prev parent reply other threads:[~2015-08-28 13:15 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 [this message]
2015-08-28 13:35 ` Thomas Petazzoni
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=180102384.TlRWI16dqe@raillard-dv6 \
--to=public.douglas.raillard@gmail.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