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:23:51 +0200 [thread overview]
Message-ID: <20140609142351.47e08090@free-electrons.com> (raw)
In-Reply-To: <1402309581-18430-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 9 Jun 2014 12:26:21 +0200, Yann E. MORIN wrote:
> -comment "libbsd needs a toolchain w/ threads"
> +comment "libbsd needs an (e)glibc toolchain w/ threads"
> depends on ( BR2_i386 || BR2_x86_64 )
> - depends on !BR2_TOOLCHAIN_HAS_THREADS
> + depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_TOOLCHAIN_USES_GLIBC
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?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-09 12:23 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 [this message]
2014-06-09 12:32 ` Yann E. MORIN
2014-06-09 12:40 ` 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=20140609142351.47e08090@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.