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] [PATCH] package/libbsd: needs an (e)glibc toolchain
Date: Mon, 9 Jun 2014 14:40:44 +0200	[thread overview]
Message-ID: <20140609144044.403d45cc@free-electrons.com> (raw)
In-Reply-To: <20140609123222.GD3512@free.fr>

Dear Yann E. MORIN,

On Mon, 9 Jun 2014 14:32:22 +0200, Yann E. MORIN wrote:

> > Is it possible to have a glibc toolchain without threads? I think no.
> > In this case, what is our policy? Should we keep both the glibc and
> > thread dependencies?
> 
> Indeed, Buildroot considers glibc toolchains have threads.
> 
> Just for this commit, I would not care we remove the threads dependency,
> since it is implicit with glibc.
> 
> However, as I said, libbsd is an Nth-level dependency of QEMU, which I
> am still p[lanning on submitting. Having static qemu-user programs is
> very usefull to run foreign chroots, and is only possible with uClibc,
> so I will have to fix that issue at some point in time. And keeping the
> threads dependency will just be a warning to me at that point.

Ok, makes sense.

> Do you want me to respin?

Nah, that's fine.

Remember that we now have musl support, and musl supports static
linking, so it could be an alternative to uClibc for some of these use
cases :-)

Best regards,

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

      reply	other threads:[~2014-06-09 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 10:26 [Buildroot] [PATCH] package/libbsd: needs an (e)glibc toolchain Yann E. MORIN
2014-06-09 12:23 ` Thomas Petazzoni
2014-06-09 12:32   ` Yann E. MORIN
2014-06-09 12:40     ` Thomas Petazzoni [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=20140609144044.403d45cc@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