From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] toolchain: introduce a toolchain knob for NPTL
Date: Mon, 17 Feb 2014 08:11:54 +0100 [thread overview]
Message-ID: <5301B63A.5000304@mind.be> (raw)
In-Reply-To: <1392297727-17627-2-git-send-email-thomas.petazzoni@free-electrons.com>
On 13/02/14 14:22, Thomas Petazzoni wrote:
> As our architecture support expands to a number of architectures that
> do not implement NPTL threading, and the number of packages that
> depend on NPTL specific features, it has become necessary to be able
> to know whether the toolchain has NPTL support or not.
>
> This commit adds a new BR2_TOOLCHAIN_HAS_THREADS_NPTL hidden Config.in
> option that allows packages to know whether NPTL is available or not.
>
> This hidden option is:
>
> * Automatically enabled when glibc/eglibc or musl toolchains are
> used, either internal or external.
>
> * Automatically enabled when an internal uClibc toolchain with NPTL
> support is configured. It is left disabled otherwise for internal
> uClibc toolchains.
>
> * Configured according to a visible Config.in option for custom
> external uClibc toolchains.
I think there is very little reason left to use NPTL on archs that
support it, isn't there? So I would first remove the option completely
for these architectures. That would also make adding a comment
unnecessary (since it becomes an architecture feature rather than a
toolchain option).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-17 7:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 13:22 [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 1/6] toolchain: introduce a " Thomas Petazzoni
2014-02-17 7:11 ` Arnout Vandecappelle [this message]
2014-02-17 8:03 ` Thomas Petazzoni
2014-02-17 16:59 ` Arnout Vandecappelle
2014-02-17 22:51 ` Thomas Petazzoni
2014-02-17 22:08 ` Arnout Vandecappelle
2014-02-17 22:57 ` Thomas Petazzoni
2014-02-17 23:09 ` Arnout Vandecappelle
2014-02-13 13:22 ` [Buildroot] [PATCH 2/6] docs/manual: indicate how to handle BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:46 ` Thomas De Schampheleire
2014-02-13 13:55 ` Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 3/6] rt-tests: use BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 4/6] sconeserver: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 5/6] tvheadend: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 6/6] qt5: needs NPTL threads Thomas Petazzoni
2014-02-13 13:46 ` [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Mike Zick
2014-02-18 21:06 ` 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=5301B63A.5000304@mind.be \
--to=arnout@mind.be \
--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.