From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] uclibc: adapt thread implementation selection to uClibc-ng
Date: Sun, 8 Mar 2015 09:45:16 +0100 [thread overview]
Message-ID: <20150308084516.GA4184@free.fr> (raw)
In-Reply-To: <20150308084044.4a135752@free-electrons.com>
Thomas, All,
On 2015-03-08 08:40 +0100, Thomas Petazzoni spake thusly:
> On Sat, 7 Mar 2015 18:39:28 +0100, Yann E. MORIN wrote:
> > > config BR2_UCLIBC_NG_VERSION_1_0_0
> > > bool "uClibc-ng 1.0.0"
> > > + select BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS \
> > > + if BR2_arc || BR2_m68k
> > > + select BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS_OLD \
> > > + if BR2_arc || BR2_bfin || BR2_m68k
> > > + select BR2_UCLIBC_VERSION_SUPPORTS_NPTL \
> > > + if !BR2_arc && !BR2_bfin && !BR2_x86_i386
> >
> > From what I can see, uclibc-ng on branch 1.0 :
> >
> > LT.old LT NPTL Notes
> > arc - - Y
>
> Ah, right, I missed that. So it means that right now we can't build an
> ARC toolchain with uClibc-ng in Buildroot: the ARC compiler version we
> use does not have TLS support, which is required for NPTL. So ARC +
> uClibc-ng is not possible right now.
>
> > arm Y - Y
>
> Yes, but Waldemar's wish is basically to not use LT or LT.old when
> there is NPTL support available. Which I believe makes sense. See his
> patch at http://patchwork.ozlabs.org/patch/446288/ where he was making
> LT and LT.old not available on ARM and ARMeb.
Eh, I never said we _had_ to have LT/LT.old when NPTL is available. ;-)
> > bfin Y Y -
>
> Correct. That needs to be fixed in my patch.
>
> > i386 - - -
> > i?86 - - Y except i386
> > m68k Y Y -
> > microblaze Y Y - not used in BR
> > mips - - Y
> > nios2 Y Y - not used in BR
> > powerpc - - Y
> > sh - - Y
> > sparc - - Y
> > x86_64 - - Y
> > xtensa - - Y
> >
> >
> > So, I guess your selection is incorrect, and you should have:
> >
> > select BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS \
> > if BR2_bfin || BR2_m68k
> > select BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS_OLD \
> > if BR2_bfin || BR2_m68k || BR2_arm || BR2_armeb
> > select BR2_UCLIBC_VERSION_SUPPORTS_NPTL \
> > if !BR2_bfin && !BR2_m68k && !BR2_x86_i386
>
> Ok, except the ARM case where I disagree (see above), and handling the
> ARC situation, I'm OK with your proposal.
OK. One more thing: since uClibc-ng supports microblaze and nios2, we
could enable uClibc (as in "uClibc in Buildroot") to build Buildroot
toolchains for those two archs, no?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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:[~2015-03-08 8:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 13:39 [Buildroot] [PATCH 0/3] uClibc-ng related fixes Thomas Petazzoni
2015-03-07 13:39 ` [Buildroot] [PATCH 1/3] uclibc: adapt thread implementation selection to uClibc-ng Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 16:41 ` Thomas Petazzoni
2015-03-07 17:20 ` Waldemar Brodkorb
2015-03-08 7:41 ` Thomas Petazzoni
2015-03-09 8:27 ` Alexey Brodkin
2015-03-09 9:46 ` Thomas Petazzoni
2015-03-07 17:39 ` Yann E. MORIN
2015-03-08 7:40 ` Thomas Petazzoni
2015-03-08 8:45 ` Yann E. MORIN [this message]
2015-03-08 9:13 ` Waldemar Brodkorb
2015-03-07 13:39 ` [Buildroot] [PATCH 2/3] uclibc: remove bogus comment about thread implementation selection Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 13:40 ` [Buildroot] [PATCH 3/3] uclibc: add patch fixing non-threaded build on Xtensa for uClibc-ng 1.0.0 Thomas Petazzoni
2015-03-07 14:40 ` Yann E. MORIN
2015-03-07 15:43 ` Waldemar Brodkorb
2015-03-07 15:50 ` Yann E. MORIN
2015-03-07 16:30 ` Thomas Petazzoni
2015-03-07 17:56 ` Waldemar Brodkorb
2015-03-08 7:35 ` Thomas Petazzoni
2015-03-07 16:29 ` 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=20150308084516.GA4184@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox