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: Wed, 29 Oct 2014 10:05:04 +0000 [thread overview]
Message-ID: <5450BBD0.4030207@imgtec.com> (raw)
In-Reply-To: <545012E2.2000604@mind.be>
Dear all,
On 10/28/2014 10:04 PM, Arnout Vandecappelle wrote:
> On 28/10/14 18:23, Vicente Olivert Riera wrote:
>> Dear all,
>>
>> On 10/28/2014 05:18 PM, Gustavo Zacarias wrote:
>>> On 10/28/2014 02:17 PM, Vicente Olivert Riera wrote:
>>>
>>>> You are right, the dependences should be propagated to those packages. I
>>>> will respin a new version.
>>>>
>>>> My apologies for that.
>>>
>>> It's more of an open question, i don't think we want to go dependency
>>> hell on this.
>>> We could probably just disable debugging for the particular package on
>>> the particular conditions i think.
>>> Regards.
>>
>> Uhm..., yeah, to be honest that was my first thought when I found what was the
>> problem.
>>
>> I'm fine with that. Let's wait until some other developers say their opinion as
>> well.
>
> I agree that that is the way to go: disable debug on the architectures that
> have a problem with it.
>
>
> Regards,
> Arnout
>
>>
>> Best regards,
Thanks for your opinion Arnout.
Patch v2 sent: http://patchwork.ozlabs.org/patch/404494/
Best regards,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
prev parent reply other threads:[~2014-10-29 10:05 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
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 [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=5450BBD0.4030207@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