From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6230] New: Cannot compile gcc without threads
Date: Sat, 4 May 2013 05:11:48 +0000 (UTC) [thread overview]
Message-ID: <bug-6230-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6230
Summary: Cannot compile gcc without threads
Product: buildroot
Version: 2012.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: a.nielsen at shikadi.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4874
--> https://bugs.busybox.net/attachment.cgi?id=4874
buildroot config to generate error
Since uClibc can't be compiled with threads (bug 6224), it must be compiled
without thread support.
However then gcc-final can't be compiled because it cannoy find pthread.h:
In file included from buildroot/toolchain/gcc-4.8.0/libgcc/gthr.h:148:0,
from buildroot/toolchain/gcc-4.8.0/libgcc/libgcov.c:31:
./gthr-default.h:35:21: fatal error: pthread.h: No such file or directory
#include <pthread.h>
^
compilation terminated.
make[3]: *** [_gcov.o] Error 1
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-05-04 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 5:11 bugzilla at busybox.net [this message]
2013-05-04 5:13 ` [Buildroot] [Bug 6230] Cannot compile gcc without threads bugzilla at busybox.net
2014-02-13 13:51 ` bugzilla at busybox.net
2014-02-13 14:38 ` [Buildroot] [Bug 6230] Cannot compile gcc without threads (uClibc-based) bugzilla at busybox.net
2014-05-06 20:23 ` bugzilla at busybox.net
2014-05-07 7:22 ` bugzilla at busybox.net
2014-07-16 17:01 ` 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-6230-163@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.