Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] audiofile: does not build with static-only
Date: Sun, 25 May 2014 18:29:01 -0300	[thread overview]
Message-ID: <5382609D.9030909@zacarias.com.ar> (raw)
In-Reply-To: <538259D0.4090008@lucaceresoli.net>

On 05/25/2014 06:00 PM, Luca Ceresoli wrote:

> Ah, I see, I hadn't followed that discussion and was not aware of such
> work you're doing. Sorry for the noise and thanks for the detailed
> clarification.
> 
> I understand the solution won't land in 2014.05.
> I wonder what's the best thing to do in cases like this to make users
> aware what there's a known bug in a release.
> 
> Should audiofile depend on BROKEN if BR2_PREFER_STATIC_LIB? This way it
> would disappear from both the user's sight and the autobuilders, but
> still visible via menuconfig search.
> 
> Or should we just add a comment that depends on audiofile and
> BR2_PREFER_STATIC_LIB?
> 
> I think the former (o the sum of the two) is preferred. It would stop
> polluting the autobuilders with known bugs and track the issue via
> `git grep BROKEN`.
> 
> Helping in fixing this bug is out of reach for me, but I can at least
> send a patch for BROKEN if it's the proper way to go.

Doing anything for 2014.05 at this point would be band aid, audiofile is
the usual failing package because it sorts nicely at the beginning, but
there are other packages that will show up if it's blacklisted.
Maybe removing static builds from the testing rotation would be nice,
but then we want to find broken stuff :)
Regards.

  reply	other threads:[~2014-05-25 21:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 14:24 [Buildroot] [PATCH] audiofile: does not build with static-only Luca Ceresoli
2014-05-24 16:45 ` Thomas Petazzoni
2014-05-24 23:13   ` Gustavo Zacarias
2014-05-25 20:39     ` Peter Korsgaard
2014-05-25 21:00     ` Luca Ceresoli
2014-05-25 21:29       ` Gustavo Zacarias [this message]
2014-05-28 16:15       ` Arnout Vandecappelle
2014-05-29  7:54         ` Thomas Petazzoni
2014-05-26  9:34     ` Thomas Petazzoni

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=5382609D.9030909@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