Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup #10: triaging proposal
Date: Sun, 29 Jun 2014 11:01:10 +0200	[thread overview]
Message-ID: <20140629110110.38f06de5@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LWVLLjPHwjLX1tYKf8BSvnt2TpGq=P5oO+MFvf2P_QnUQ@mail.gmail.com>

Dear Thomas De Schampheleire,

On Sun, 29 Jun 2014 10:35:06 +0200, Thomas De Schampheleire wrote:

> > If this gets applied, it needs to go together with
> > http://patchwork.ozlabs.org/patch/319108/. However, I'd like to see a
> > solution that merges the existing qemu package with the qemu-system
> > package proposed by Gustavo.
> 
> That's fine too. In this case we should mark it as D and add it to the
> Buildroot TODO list. Maybe Gustavo could look into it...

I think Gustavo is not that much interested into merging his
qemu-system package with the existing qemu package. We had a bit of
discussion about this a few weeks ago, and it seems like someone else
needs to step up and offer a proper patch series based on Frank patches
for qemu user, and Gustavo patches for qemu system.

> >> I would guess the same decision as the previous patch applies here:
> >> B reject
> >
> > Yeah, same problem. Maybe my previous opinion is wrong, and we should
> > just patch Buildroot's uClibc as needed, and not exclude all
> > problematic packages from being used with an external uClibc toolchain.
> 
> but then they'll continue to fail with external toolchains, right?

Well, we would not allow the selection of the problematic packages with
external uClibc toolchains. It's sad because it means people building a
toolchain with Buildroot and then re-using it as an external toolchain
will no longer be able to build certain packages.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-06-29  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 20:02 [Buildroot] Patchwork cleanup #10: triaging proposal Thomas De Schampheleire
2014-06-14 20:09 ` Thomas De Schampheleire
2014-06-15  5:47 ` Thomas De Schampheleire
2014-06-28 18:45 ` Thomas De Schampheleire
2014-06-28 20:08 ` Thomas Petazzoni
2014-06-29  8:35   ` Thomas De Schampheleire
2014-06-29  9:01     ` Thomas Petazzoni [this message]
2014-06-30  7:44   ` Paul Cercueil
2014-07-02  9:01   ` Paul Cercueil

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=20140629110110.38f06de5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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