From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: mask uclibc-ng for xtensa
Date: Tue, 03 Mar 2015 19:08:34 -0300 [thread overview]
Message-ID: <54F630E2.5040703@zacarias.com.ar> (raw)
In-Reply-To: <54F62886.5090506@zacarias.com.ar>
On 03/03/2015 06:32 PM, Gustavo Zacarias wrote:
> On 03/03/2015 06:26 PM, Peter Korsgaard wrote:
>
>>>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
>>
>> > Is broken like plain uClibc, fixes:
>> > http://autobuild.buildroot.net/results/77f/77fe89d358a90f5167e58bedb73495d7ee9a7f5d/
>>
>> So why do we have:
>>
>> commit 060125b4fed11458288b14fbd2d49e1c12eb11df
>> Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>> Date: Sat Feb 14 22:01:07 2015 +0100
>>
>> uclibc: enable Xtensa NPTL support with uClibc-ng
>>
>> Then? Presumably something was working when this was done?
>
> Autobuilders are speaking up, i gave uclibc a quick look and xtensa
> elfinterp.c is the only arch including dl-tls.h
> I'll try droppping that, it doesn't make sense that the interpreter
> needs tls, but for the time being i'd nuke uclibc-ng for xtensa pending
> testing/upstream aproval.
> Regards.
Digging up a little more the scenario is:
uclibc-ng -> nptl (old threads broken, none possibly as well)
uclibc -> no nptl, only old or none.
So basically apply the patch i say, it's not an option we had shipping
and uclibc-ng git reverts (and re-reverts!) this so we should wait for a
new release to know what's up and let them make up their mind.
Regards.
next prev parent reply other threads:[~2015-03-03 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 20:53 [Buildroot] [PATCH] uclibc: mask uclibc-ng for xtensa Gustavo Zacarias
2015-03-03 21:26 ` Peter Korsgaard
2015-03-03 21:32 ` Gustavo Zacarias
2015-03-03 22:08 ` Gustavo Zacarias [this message]
2015-03-04 10:55 ` Waldemar Brodkorb
2015-03-04 12:19 ` Gustavo Zacarias
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=54F630E2.5040703@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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