From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Makefile: add check of binaries architecture
Date: Sun, 12 Mar 2017 18:54:43 +0100 [thread overview]
Message-ID: <20170312175443.GD3739@free.fr> (raw)
In-Reply-To: <20170312182913.0c6dc2cd@free-electrons.com>
Thomas, All,
On 2017-03-12 18:29 +0100, Thomas Petazzoni spake thusly:
> 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.
I agree.
> Could you be more specific about these firmware files? Where are they
> located?
In theory, those kind of files may be located anywhere, but in this
specific case, it is in /lib/firmware.
The firmware files could be moved elsewhere, of course, but:
1) /lib/firmware is the "standard" location for firmware files;
2) a binary-only tool can be used to load the firmware and could
expect it to be located there.
> Perhaps with a test restricted to {usr,}/{bin,sbin,lib}, we can avoid
> testing those firmware files.
I think this would be sensible, as long as /lib/firmware is excluded, as
well as /usr/lib/firmware (in case of merged /usr).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-03-12 17:54 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 [this message]
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=20170312175443.GD3739@free.fr \
--to=yann.morin.1998@free.fr \
--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