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: Sun, 2 Apr 2017 14:30:20 +0200 [thread overview]
Message-ID: <20170402143020.06ef773c@free-electrons.com> (raw)
In-Reply-To: <0u07rdxu5j.ln2@ID-313208.user.individual.net>
Hello,
On Sun, 02 Apr 2017 12:38:24 +0200, Bernd Kuhls wrote:
> http://autobuild.buildroot.net/results/de7/
> de7079b89fda1dd47e52619a644f23c4f4986b2c//
>
> ERROR: architecture for "/usr/lib/libmpeg2convert.so.0.0.0" is "Sparc v8
> +", should be "Sparc"
> ERROR: architecture for "/usr/lib/libmpeg2.so.0.1.0" is "Sparc v8+",
> should be "Sparc"
>
> http://autobuild.buildroot.net/results/f96/
> f96c30c5c398db1ba561740ae64e922cd4f8a524//
>
> ERROR: architecture for "/usr/lib/libopenblas_sparcp-r0.2.19.dev.so" is
> "Sparc v8+", should be "Sparc"
>
> Patching arch/Config.in.sparc like this
>
> @@ -30,5 +30,6 @@ config BR2_GCC_TARGET_CPU
> default "ultrasparc" if BR2_sparc_v9
>
> config BR2_READELF_ARCH_NAME
> + default "Sparc v8+" if BR2_sparc_v8
> default "Sparc" if BR2_sparc
> default "Sparc v9" if BR2_sparc64
No, that's not the proper fix.
I had a look at the libmpeg2 problem yesterday. The issue is that the
configure.ac script forces -mcpu=ultrasparc -mvis, which generates
Sparcv8+ code. However, simply removing those flags doesn't work, as it
then tries to build some code that really needs the Sparc VIS
instructions.
Apparently, the libmpeg2 code is smart enough to decide at runtime if
the VIS instructions are supported or not, so even though the code is
for Sparc v8+, it's safe to run it on older Sparc machines. That's
clearly a case where the check we make on the file architecture is a
bit annoying.
I don't yet have a good solution for this case. Suggestions welcome.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-02 12:30 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 [this message]
2017-04-03 14:24 ` Arnout Vandecappelle
2017-04-03 15:08 ` Thomas Petazzoni
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=20170402143020.06ef773c@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