From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lame: Disable for Aarch64 and MIPS when building with debug symbols
Date: Tue, 28 Oct 2014 17:17:34 +0000 [thread overview]
Message-ID: <544FCFAE.3050806@imgtec.com> (raw)
In-Reply-To: <544FCF49.5010704@zacarias.com.ar>
On 10/28/2014 05:15 PM, Gustavo Zacarias wrote:
> On 10/28/2014 02:05 PM, Vicente Olivert Riera wrote:
>
>> Building lame with debug symbols needs the following macros to be
>> defined: _FPU_MASK_IM, _FPU_MASK_ZM, _FPU_MASK_OM.
>> If BR2_ENABLE_DEBUG is selected, then we have to disable lame for
>> Aarch64 and MIPS because these architectures don't have those macros
>> defined.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/721/721dff299b204b1d3ccc0846009eb17faa2d29eb/
>>
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>> ---
>> package/lame/Config.in | 7 +++++++
>> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> What happens when another package that uses lame selects it? (like mpd,
> gst-plugins-ugly, gst1-plugins-ugly).
> Regards.
>
You are right, the dependences should be propagated to those packages. I
will respin a new version.
My apologies for that.
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-10-28 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:05 [Buildroot] [PATCH] lame: Disable for Aarch64 and MIPS when building with debug symbols Vicente Olivert Riera
2014-10-28 17:15 ` Gustavo Zacarias
2014-10-28 17:17 ` Vicente Olivert Riera [this message]
2014-10-28 17:18 ` Gustavo Zacarias
2014-10-28 17:23 ` Vicente Olivert Riera
2014-10-28 22:04 ` Arnout Vandecappelle
2014-10-29 10:05 ` Vicente Olivert Riera
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=544FCFAE.3050806@imgtec.com \
--to=vincent.riera@imgtec.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