Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtasn1: bump to version 4.6
Date: Tue, 15 Sep 2015 09:56:47 +0200	[thread overview]
Message-ID: <20150915095647.140ee099@free-electrons.com> (raw)
In-Reply-To: <55F74581.5070301@mind.be>

Arnout,

On Tue, 15 Sep 2015 00:09:05 +0200, Arnout Vandecappelle wrote:

>  file has the advantage of also working for scripts, and should even work for
> FLAT binaries (which readelf wouldn't like). But it doesn't show the CPU, ISA
> and FP details, which are useful to check as well.
> 
>  So the perfect approach would be: file, and readelf if file says it's an ELF.

Right.

>  Or, of course, python-magic and python-pyelftools :-)

Indeed, but then we would have to make the test optional so that
Buildroot can continue to work on systems where those additional Python
modules are not available. Which isn't as good as an unconditional
test that relies on already available utilities.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-15  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 22:24 [Buildroot] [PATCH] libtasn1: bump to version 4.6 Gustavo Zacarias
2015-09-12  9:26 ` Vicente Olivert Riera
2015-09-13 10:12   ` Thomas Petazzoni
2015-09-13 19:52     ` Peter Korsgaard
2015-09-13 21:20       ` Thomas Petazzoni
2015-09-14  8:49         ` Vicente Olivert Riera
2015-09-14 22:09         ` Arnout Vandecappelle
2015-09-15  7:56           ` Thomas Petazzoni [this message]
2015-09-13 10:07 ` 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=20150915095647.140ee099@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