Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/elf2flt: .ARM.exidx RO data section is incorrectly mapped to data
Date: Wed, 6 Nov 2019 22:51:25 +0100	[thread overview]
Message-ID: <20191106225125.7be919ad@windsurf> (raw)
In-Reply-To: <20191106211913.21256-1-romain.naour@smile.fr>

On Wed,  6 Nov 2019 22:19:13 +0100
Romain Naour <romain.naour@smile.fr> wrote:

> Starting with Binutils 2.33.1, elf2flt segfault while building busybox:
> "ld (ld-elf2flt):
> /opt/armv7m--uclibc--bleeding-edge-2/arm-buildroot-uclinux-uclibcgnueabi/bin/elf2flt
> 
> This was reported to the Binutils mailing list and it's seems
> an elf2flt issue with .ARM.exidx RO data section as explained
> by: https://sourceware.org/ml/binutils/2019-10/msg00132.html
> 
> Apply the patch provided by Greg Ungerer [1] and tested by
> Christophe Priouzeau using stm32f469_disco_defconfig on
> stm32f469-disco board.
> 
> Fixes:
> https://gitlab.com/kubu93/toolchains-builder/-/jobs/319395300
> 
> [1] https://github.com/uclinux-dev/elf2flt/issues/12
> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> Cc: Christophe Priouzeau <christophe.priouzeau@st.com>

Thanks a lot for this patch! Good to see that some people are active
maintaining elf2flt.

While you're in touch with people with elf2flt knowledge, could you
have a look at
http://lists.busybox.net/pipermail/buildroot/2019-June/253203.html ?
I'm pretty sure for someone with ARM/elf2flt knowledge it's fairly easy
to fix.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-06 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 21:19 [Buildroot] [PATCH] package/elf2flt: .ARM.exidx RO data section is incorrectly mapped to data Romain Naour
2019-11-06 21:51 ` Thomas Petazzoni [this message]
2019-11-09 17:52 ` 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=20191106225125.7be919ad@windsurf \
    --to=thomas.petazzoni@bootlin.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