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:55:58 +0000 [thread overview]
Message-ID: <bug-8766-163-KrIr9Yrq7m@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 #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
(In reply to Thomas Petazzoni from comment #1)
> 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.
I just tested, it also fails with the same error on i486 with thread support
disabled. I.E this defconfig:
BR2_x86_i486=y
BR2_PTHREADS_NONE=y
fails to build with:
../../../libgcc/generic-morestack-thread.c:41:21: fatal error: pthread.h: No
such file or directory
#include <pthread.h>
^
compilation terminated.
make[4]: *** [generic-morestack-thread.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [all-target-libgcc] Error 2
make[2]: *** [all] Error 2
make[1]: ***
[/home/test/outputs/i486-nothread/build/host-gcc-final-4.9.3/.stamp_built]
Error 2
make: *** [_all] Error 2
--
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:55 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 ` [Buildroot] [Bug 8766] " bugzilla at busybox.net
2016-03-06 12:55 ` bugzilla at busybox.net [this message]
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-KrIr9Yrq7m@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox