From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Makefile: add check of binaries architecture
Date: Sun, 12 Mar 2017 18:29:13 +0100 [thread overview]
Message-ID: <20170312182913.0c6dc2cd@free-electrons.com> (raw)
In-Reply-To: <20170312151543.GC3739@free.fr>
Hello,
On Sun, 12 Mar 2017 16:15:43 +0100, Yann E. MORIN wrote:
> 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.
I don't think I want to give up that easily on this, especially
considering how many times we get submission for packages that are not
actually cross-compiled.
Could you be more specific about these firmware files? Where are they
located?
Perhaps with a test restricted to {usr,}/{bin,sbin,lib}, we can avoid
testing those firmware files.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-12 17:29 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 [this message]
2017-03-12 17:54 ` Yann E. MORIN
2017-03-12 17:31 ` Baruch Siach
2017-03-12 19:03 ` Peter Seiderer
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=20170312182913.0c6dc2cd@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