From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "uClibc: port linuxthreads errnopatch to 0.9.33.2"
Date: Wed, 06 Mar 2013 18:44:14 +0100 [thread overview]
Message-ID: <5137806E.4020507@mind.be> (raw)
In-Reply-To: <87lia39c5g.fsf@dell.be.48ers.dk>
On 03/04/13 20:51, Peter Korsgaard wrote:
>>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
>
> Sagaert> Hi
>
> Sagaert> It took some time till I could verify it against real hardware.
>
> Sagaert> I switched to NTPL and so far got no problems with any package.
>
> Sagaert> It's a bit mysterious when to use the other options (pthreads
> Sagaert> and pthreads old). Incompatible packages mostly do build, but
> Sagaert> the problems show up at runtime.
>
> The pthreads options are basically just there for legacy reasons (from
> before NPTL existed) and presumably see very little testing these
> days. We should aguable deprecate them.
That would be a good idea. For who really wants it, there is still the
crosstool-NG toolchain.
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:[~2013-03-06 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 14:09 [Buildroot] [PATCH] Revert "uClibc: port linuxthreads errno patch to 0.9.33.2" Gustavo Zacarias
2013-02-21 14:18 ` Peter Korsgaard
2013-02-22 12:39 ` [Buildroot] [PATCH] Revert "uClibc: port linuxthreads errnopatch " Sagaert Johan
2013-02-22 12:44 ` Gustavo Zacarias
2013-03-04 19:46 ` Sagaert Johan
2013-03-04 19:51 ` Peter Korsgaard
2013-03-06 17:44 ` Arnout Vandecappelle [this message]
2013-03-07 8:52 ` Peter Korsgaard
2013-03-07 9:29 ` Sagaert Johan
2013-03-07 9:34 ` Thomas Petazzoni
2013-03-07 9:44 ` Simon Dawson
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=5137806E.4020507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox