From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: proper thread default on m68k and Microblaze
Date: Sun, 7 Aug 2016 22:15:52 +0200 [thread overview]
Message-ID: <20160807201552.GG5855@free.fr> (raw)
In-Reply-To: <1470414941-29826-1-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2016-08-05 18:35 +0200, Thomas Petazzoni spake thusly:
> Traditionally, Buildroot has a default of enabling thread
> support. However, with the current construct of the thread choice in the
> uclibc package, the m68k and microblaze architecture end up with no
> thread support as the default.
>
> In order to avoid having to explicit a more complicated "default" value
> for the choice, we take a simple approach:
>
> - The "none" choice is moved at the end of the list, so that it is not
> selected as the default unless there is really no other thread
> implementation available.
>
> - We make NPTL the default thread implementation.
>
> - On architectures where NPTL is not available, the NPTL option will
> not be available, so Kconfig will automatically fallback to
> linuxthreads.
And to make things even more simple, why not move NPTL first, then LT,
then none, and remove the default?
Thus, when NPTL is avbailable, it is used; if not, LT is used; if not,
then none is used.
Regards,
Yann E. MORIN.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> package/uclibc/Config.in | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/package/uclibc/Config.in b/package/uclibc/Config.in
> index 7c99195..b7714d4 100644
> --- a/package/uclibc/Config.in
> +++ b/package/uclibc/Config.in
> @@ -47,15 +47,13 @@ config BR2_TOOLCHAIN_BUILDROOT_LOCALE
>
> choice
> prompt "Thread library implementation"
> + # Use NPTL when available. If not available, kconfig will
> + # automatically fall back to linuxthreads.
> default BR2_PTHREADS_NATIVE
> - default BR2_PTHREADS if !BR2_USE_MMU
> help
> Use this option to select the thread library implementation
> that should be used in your toolchain.
>
> - config BR2_PTHREADS_NONE
> - bool "none"
> -
> config BR2_PTHREADS
> bool "linuxthreads"
> select BR2_TOOLCHAIN_HAS_THREADS
> @@ -67,6 +65,10 @@ choice
> select BR2_TOOLCHAIN_HAS_THREADS_NPTL
> depends on BR2_USE_MMU
> depends on !BR2_m68k && !BR2_microblaze
> +
> + config BR2_PTHREADS_NONE
> + bool "none"
> +
> endchoice
>
> config BR2_PTHREAD_DEBUG
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-07 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 16:35 [Buildroot] [PATCH] uclibc: proper thread default on m68k and Microblaze Thomas Petazzoni
2016-08-07 12:21 ` Waldemar Brodkorb
2016-08-07 20:15 ` Yann E. MORIN [this message]
2016-08-07 21:04 ` Thomas Petazzoni
2016-08-07 21:04 ` 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=20160807201552.GG5855@free.fr \
--to=yann.morin.1998@free.fr \
--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.