From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8766] Compiling host-gcc-final-4.9.3 broken on i386
Date: Sun, 06 Mar 2016 12:51:15 +0000 [thread overview]
Message-ID: <bug-8766-163-Tc1s7yr72M@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8766-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8766
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks Bernd for the report. This is an issue you already reported in the past,
I found your previous report and some related discussion at
https://patchwork.ozlabs.org/patch/484002/.
Basically, as I understand it, the problem is that uClibc-ng only offers the
NPTL thread implementation for x86. But since i386 does not have the necessary
instructions to implement NPTL, we only offer the "none" thread implementation,
which explains why <pthread.h> is missing.
So I think there are really two questions here:
1/ Is it correct that uClibc-ng provides no thread implementation at all for
i386. This is something to discuss with Waldemar.
2/ Are we also seeing this <pthread.h> missing problem when building with no
threads on i486+. If we also have this problem, then I don't see how the "none"
thread implementation can still be useful.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-03-06 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 11:08 [Buildroot] [Bug 8766] New: Compiling host-gcc-final-4.9.3 broken on i386 bugzilla at busybox.net
2016-03-06 12:51 ` bugzilla at busybox.net [this message]
2016-03-06 12:55 ` [Buildroot] [Bug 8766] " bugzilla at busybox.net
2016-03-06 13:27 ` bugzilla at busybox.net
2016-03-08 21:07 ` bugzilla at busybox.net
2016-04-19 21:26 ` bugzilla at busybox.net
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=bug-8766-163-Tc1s7yr72M@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.