From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] arp-scan: new package
Date: Wed, 5 Apr 2017 18:34:45 +0200 [thread overview]
Message-ID: <20170405183445.6cde0af8@free-electrons.com> (raw)
In-Reply-To: <20170405101410.27980-1-arnout@mind.be>
Hello,
On Wed, 5 Apr 2017 12:14:10 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> On the br-arm-cortex-m4-full toolchain, the build fails with a
> segmentation fault in elf2flt, so add an exception for ARM FLAT
> toolchains. Other FLAT toolchains (e.g. br-m68k-5208-full) work fine.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> I tried to debug the elf2flt segfault but elf2flt isn't exactly the
> most low-entry-bar source code...
I think we have a regression here, which I would point to the bump of
binutils from 2.26 to 2.27. Indeed, several packages are now causing
segfaults in elf2flt on ARM:
Busybox:
http://autobuild.buildroot.net/results/475/4758354f0e2f7f127c1a99ef7846eb62f5ce41b5/build-end.log
pcre:
http://autobuild.buildroot.net/results/68c/68cf951594b0e67b45f8711745c17b93e2fbc03e/build-end.log
and I'm sure the list will grow. So I believe that binutils 2.27
produces binaries that are a bit different, and confuse elf2flt.
Looking at https://github.com/uclinux-dev/elf2flt/commits/master, I
don't see anything that particular stands out.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-05 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 10:14 [Buildroot] [PATCH v2] arp-scan: new package Arnout Vandecappelle
2017-04-05 16:34 ` Thomas Petazzoni [this message]
2017-04-06 8:26 ` Arnout Vandecappelle
2017-04-06 8:33 ` Thomas Petazzoni
2017-04-06 8:42 ` Arnout Vandecappelle
2017-04-06 9:55 ` Thomas Petazzoni
2017-04-08 18:03 ` Waldemar Brodkorb
2017-04-10 8:06 ` Arnout Vandecappelle
2017-04-05 21:12 ` 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=20170405183445.6cde0af8@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