From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Revert "uClibc: port linuxthreads errnopatch to 0.9.33.2"
Date: Fri, 22 Feb 2013 09:44:03 -0300 [thread overview]
Message-ID: <51276813.7050604@zacarias.com.ar> (raw)
In-Reply-To: <CFB67F3F72BB450DAF0C0E10C27DFC00@JohanW7>
On 02/22/2013 09:39 AM, Sagaert Johan wrote:
> Hi
>
> I saw this patch was reverted, so I wonder is there (already or in the making) a way so I can point to a directory in the buildroot
> configuration where I have additional ?Clibc patches and a 'series' file ? (similar like the infrastructure for the kernel patches.)
> Annoying problem anyway, my app fails at runtime without the patch.
>
> Johan
Hi.
Out of curiosity why don't you want to use NPTL with the latest uClibc?
If i remember correctly using anything other than NPTL is not recommended.
You could use a trick similar to
toolchain/gcc/*/powerpc-link-with-math-lib.patch.conditional for this
patch but in a reverse fashion (the gcc patch is applied for powerpc
only, you could apply for everything except sparc, though you'd had to
check if it's the only affected arch - it's a build issue so it
shouldn't be difficult).
The patch conditions are set in toolchain/gcc/gcc-uclibc-4.x.mk
Since the patch fixes issues i don't think Peter would disagree in
applying it.
Regards.
next prev parent reply other threads:[~2013-02-22 12: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 [this message]
2013-03-04 19:46 ` Sagaert Johan
2013-03-04 19:51 ` Peter Korsgaard
2013-03-06 17:44 ` Arnout Vandecappelle
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=51276813.7050604@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 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.