From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtasn1: bump to version 4.6
Date: Sun, 13 Sep 2015 23:20:43 +0200 [thread overview]
Message-ID: <20150913232043.415b5d1a@free-electrons.com> (raw)
In-Reply-To: <87fv2icd1d.fsf@dell.be.48ers.dk>
Peter,
On Sun, 13 Sep 2015 21:52:30 +0200, Peter Korsgaard wrote:
> > BTW, the fact that you are regularly verifying that the binaries built
> > by Buildroot are built for MIPS, I am wondering if it wouldn't be worth
> > the effort to add a final check at the end of the build to verify that
> > all binaries are built for the proper architecture/ABI. I remember that
> > some time ago, the nfs-utils package was installing binaries built for
> > the host machine into the target filesystem.
>
> Yes, it could be a nice test. How would we do it? With readelf? We would
> need to filter out any shell scripts and similar.
Either readelf, or just "file". But maybe readelf is fine as it's
available in the toolchain. We can skip scripts by testing the first
two bytes of each file and see if they are #!, no?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-13 21:20 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 [this message]
2015-09-14 8:49 ` Vicente Olivert Riera
2015-09-14 22:09 ` Arnout Vandecappelle
2015-09-15 7:56 ` Thomas Petazzoni
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=20150913232043.415b5d1a@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