From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/lame: Fix compile on 32bit Intel with gcc-4.9.x
Date: Thu, 28 Aug 2014 22:58:46 +0200 [thread overview]
Message-ID: <53FF9806.8040305@mind.be> (raw)
In-Reply-To: <20140817145508.22d9d4ed@free-electrons.com>
On 08/17/14 14:55, Thomas Petazzoni wrote:
> 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.
Since the work is done in a hook, it can be as simple as:
ifeq ($(BR2_i386),y)
define LAME_COMPILE_FIX
if $(CC) --version | grep -q '4\.9'; then \
$(SED) '/xmmintrin\.h/d' $(@D)/configure; \
fi
endef
endif
However, it should be a post-patch hook, not a pre-configure hook. The
convention is that anything that manipulates the source itself should be done in
the patch (or extract) step.
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-08-28 20:58 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
2014-08-28 20:58 ` Arnout Vandecappelle [this message]
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=53FF9806.8040305@mind.be \
--to=arnout@mind.be \
--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.