From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/script/check-bin-arch: ignore /usr/share
Date: Thu, 23 Mar 2017 09:16:23 +0100 [thread overview]
Message-ID: <20170323091623.6fcd2bb2@free-electrons.com> (raw)
In-Reply-To: <2219b1bf-ae08-5c54-5f18-6a91e9f975ba@mind.be>
Hello,
On Thu, 23 Mar 2017 00:03:57 +0100, Arnout Vandecappelle wrote:
> > >> I wonder if we shouldn't turn the tests around, E.G. instead of
> > >> searching for elf files with a machine different from target, search for
> > >> a files with machine == host.
>
> I don't agree. We don't only want to detect host-target confusion, we also want
> to detect wrong compilation, e.g. missing -EB.
This was exactly the case of the gst-ffmpeg package, for which I've
sent a fix. Everything was built for Sparc, but two libraries were
built for a slightly different version of Sparc, which was actually
incorrect.
Since for now, autobuilders issue caused by this seems to have all been
handled, I don't think there's much need to find a different solution.
Let's give it some more time and see if we need to change our mind.
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-23 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 20:35 [Buildroot] [PATCH] support/script/check-bin-arch: ignore /usr/share Thomas Petazzoni
2017-03-21 21:03 ` Yann E. MORIN
2017-03-21 21:15 ` Peter Korsgaard
2017-03-22 8:24 ` Peter Korsgaard
2017-03-22 13:06 ` Thomas Petazzoni
2017-03-22 21:43 ` Peter Korsgaard
2017-03-22 22:04 ` Thomas Petazzoni
2017-03-22 23:03 ` Arnout Vandecappelle
2017-03-23 8:16 ` Thomas Petazzoni [this message]
2017-03-28 11:50 ` Peter Korsgaard
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=20170323091623.6fcd2bb2@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