Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup #9: triaging proposal
Date: Wed, 30 Apr 2014 08:57:37 -0300	[thread overview]
Message-ID: <5360E531.706@zacarias.com.ar> (raw)
In-Reply-To: <CAAXf6LX=CTGexZ-mm1dSjBzBV77WcDUo+mzNDyk=nAfwZSLKEQ@mail.gmail.com>

On 04/30/2014 04:53 AM, Thomas De Schampheleire wrote:

> On Thu, Apr 24, 2014 at 9:46 PM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> audiofile: needs dynamic library
>> Simon Dawson <spdawson@gmail.com>
>> http://patchwork.ozlabs.org/patch/290552
>>
>> C unsure: the autobuild problem this patch is supposed to fixed is
>> still present (http://autobuild.buildroot.org/?reason=audiofile-0.3.6)
>> but the correctness of the patch has been under discussion. Gustavo
>> may possibly provide more details.
> 
> 
> Gustavo: could you provide more details about this audiofile
> situation, and what to do with the mentioned patch?

Hi.
After some testing with latest git i've got:

Blackfin external 2013R1 FLAT builds audiofile (mpd can't because nommu).
Sourcery external 2013.11 ARM builds mpd with audiofile fine.

Mipsel internal defaults (+stdc +wchar) is fine too building mpd+audiofile.

Now that libstdc++.a is being copying it seems at least some common
cases work fine.
Maybe i'm missing something?

Regards.

  reply	other threads:[~2014-04-30 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 19:46 [Buildroot] Patchwork cleanup #9: triaging proposal Thomas De Schampheleire
2014-04-24 22:21 ` Arnout Vandecappelle
2014-04-30  7:51   ` Thomas De Schampheleire
2014-04-24 22:42 ` Yann E. MORIN
2014-04-28 14:05 ` clshotwe at rockwellcollins.com
2014-04-30  7:49   ` Thomas De Schampheleire
2014-04-30  7:53 ` Thomas De Schampheleire
2014-04-30 11:57   ` Gustavo Zacarias [this message]
2014-04-30 14:23     ` Gustavo Zacarias

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=5360E531.706@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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