Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lame: Disable for Aarch64 and MIPS when building with debug symbols
Date: Tue, 28 Oct 2014 23:04:18 +0100	[thread overview]
Message-ID: <545012E2.2000604@mind.be> (raw)
In-Reply-To: <544FD129.1070402@imgtec.com>

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,


-- 
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

  reply	other threads:[~2014-10-28 22:04 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 [this message]
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=545012E2.2000604@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox