From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/lame: Fix compile on 32bit Intel with gcc-4.9.x
Date: Sun, 17 Aug 2014 14:55:08 +0200 [thread overview]
Message-ID: <20140817145508.22d9d4ed@free-electrons.com> (raw)
In-Reply-To: <XnsA38C830E65DF6berndkuhlsPkbjNfxxIA@bernd-kuhls.de>
Dear Bernd Kuhls,
On Sun, 17 Aug 2014 12:53:00 +0200, Bernd Kuhls wrote:
> I understand, but removing the gcc version check, which would remove
> support for xmmintrin.h in all i386 builds, would remove the mmx support
> for lame on many builds, where it is not necessary.
Yes, understood. Maybe instead add some conditional code in lame to
enable the MMX stuff only with known working gcc versions? I think
there are some #define you can test to get the gcc version.
> Would something like this, extended to all external toolchains, be
> acceptable?
>
> --- a/toolchain/toolchain-external/Config.in
> +++ b/toolchain/toolchain-external/Config.in
> @@ -18,6 +18,7 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM
> select BR2_INSTALL_LIBSTDCPP
> select BR2_HOSTARCH_NEEDS_IA32_LIBS
> select BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_1
> + select BR2_GCC_VERSION_4_9_X
> help
> Linaro toolchain for the ARM architecture. It uses Linaro
> GCC 2014.05 (based on gcc 4.9), Linaro GDB 2014.05 (based on
That works only for "known" external toolchains: it won't work with
custom external toolchains.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-17 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 22:18 [Buildroot] [PATCH] package/lame: Fix compile on 32bit Intel with gcc-4.9.x Bernd Kuhls
2014-08-17 7:36 ` Thomas Petazzoni
2014-08-17 10:53 ` Bernd Kuhls
2014-08-17 12:55 ` Thomas Petazzoni [this message]
2014-08-28 20:58 ` 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=20140817145508.22d9d4ed@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