From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Makefile: add check of binaries architecture
Date: Sun, 12 Mar 2017 20:03:40 +0100 [thread overview]
Message-ID: <20170312200340.4e0d356a@gmx.net> (raw)
In-Reply-To: <20170312173119.qt6mcfxkalpzaeoj@tarshish>
Hello *,
On Sun, 12 Mar 2017 19:31:19 +0200, Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Yann,
>
> On Sun, Mar 12, 2017 at 04:15:43PM +0100, Yann E. MORIN wrote:
> > On 2017-03-12 16:06 +0100, Thomas Petazzoni spake thusly:
> > > As shown recently by the firejail example, it is easy to miss that a
> > > package builds and installs binaries without actually cross-compiling
> > > them: they are built for the host architecture instead of the target
> > > architecture.
> > >
> > > This commit adds a small helper script, check-bin-arch, called from
> > > the main Makefile as a TARGET_FINALIZE_HOOKS, to verify that all ELF
> > > binaries have been built for the correct CPU architecture.
> >
> > That is not possible in all situations.
> >
> > For example, I have a board here with a kind of co-processor of a
> > different architecture; the firmware for that co-processor is loaded
> > at runtime. It is an ELF file, and it is in target/.
> >
> > So I don't think it is possible to check that all ELF files are for the
> > Buildroot-known target.
> >
> > We already discussed this a while ago and came to the same conclusiong
> > back then.
>
> Maybe limiting the check to well knows target binary directories like
> target/{bin,sbin,usr/bin,usr/sbin,...} would help. This check won't catch all
> possible locations of target ELF binaries, but it's still a significant
> improvement over the current situation.
...or limit to executable binary files (for firmware files read rights should be enough)?
Regards,
Peter
>
> baruch
>
next prev parent reply other threads:[~2017-03-12 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 15:06 [Buildroot] [PATCH 1/2] arch: add BR2_READELF_ARCH_NAME hidden config option Thomas Petazzoni
2017-03-12 15:06 ` [Buildroot] [PATCH 2/2] Makefile: add check of binaries architecture Thomas Petazzoni
2017-03-12 15:15 ` Yann E. MORIN
2017-03-12 17:29 ` Thomas Petazzoni
2017-03-12 17:54 ` Yann E. MORIN
2017-03-12 17:31 ` Baruch Siach
2017-03-12 19:03 ` Peter Seiderer [this message]
2017-03-12 19:22 ` Arnout Vandecappelle
2017-03-12 19:14 ` Arnout Vandecappelle
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=20170312200340.4e0d356a@gmx.net \
--to=ps.report@gmx.net \
--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