All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] arch: add BR2_READELF_ARCH_NAME hidden config option
Date: Mon, 3 Apr 2017 17:08:46 +0200	[thread overview]
Message-ID: <20170403170846.397bfbf0@free-electrons.com> (raw)
In-Reply-To: <eb0947cc-a940-9edc-a6fd-d324337f6568@mind.be>

Hello,

On Mon, 3 Apr 2017 16:24:55 +0200, Arnout Vandecappelle wrote:

>  So, let me get this clear: libmpeg2 actually does the right thing, and it is in
> fact possible to link the Sparc v8+ library with Sparc libraries?

It's not so much that you can link Sparc v8+ code with Sparc code that
is important:  you can link ARMv5 and ARMv7 code together, but running
ARMv7 code on ARMv5 still doesn't make sense.

And "Sparc v8+" on regular Sparc like we support is not going to work.
However, what is important here is that libmpeg is smart enough to not
call into the Sparc v8+ code if we're not on Sparc v8+.

It's exactly like having SSE3 code built-in, and testing at runtime if
SSE3 is enabled before calling the SSE3 specific code. In a Buildroot
context where we normally build for specifically the target system,
this shouldn't be necessary, but some software packages do this anyway.

>  In that case, I guess we should extend check-bin-arch to support regexes for
> the expected arch, and set the BR2_sparc arch to "Sparc( v8+)?".

Not as simple: another package may generate Sparc v8+ code, and this
would be bogus.

So, in the context of Buildroot, I believe we should rather patch
libmpeg to not generate the Sparc v8+ code if we are not on Sparc v8+.

Best regards,

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

  reply	other threads:[~2017-04-03 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 13:07 [Buildroot] [PATCH v4 1/2] arch: add BR2_READELF_ARCH_NAME hidden config option Thomas Petazzoni
2017-03-19 13:07 ` [Buildroot] [PATCH v4 2/2] Makefile: add check of binaries architecture Thomas Petazzoni
2017-03-20 21:26 ` [Buildroot] [PATCH v4 1/2] arch: add BR2_READELF_ARCH_NAME hidden config option Thomas Petazzoni
2017-04-02 10:38   ` Bernd Kuhls
2017-04-02 12:30     ` Thomas Petazzoni
2017-04-03 14:24       ` Arnout Vandecappelle
2017-04-03 15:08         ` Thomas Petazzoni [this message]
2017-04-10 15:49           ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2017-03-12 22:17 Thomas Petazzoni
2017-03-13 22:15 ` 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=20170403170846.397bfbf0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.