From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8766] New: Compiling host-gcc-final-4.9.3 broken on i386
Date: Sun, 06 Mar 2016 11:08:51 +0000 [thread overview]
Message-ID: <bug-8766-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8766
Bug ID: 8766
Summary: Compiling host-gcc-final-4.9.3 broken on i386
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: bernd.kuhls at t-online.de
CC: buildroot at uclibc.org
Target Milestone: ---
When compiling buildroot git master (c6e3511) with this defconfig
BR2_x86_i386=y
this error occurs:
/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/build/./gcc/xgcc
-B/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/build/./gcc/
-B/home/bernd/buildroot/br4_i386/output/host/usr/i386-buildroot-linux-uclibc/bin/
-B/home/bernd/buildroot/br4_i386/output/host/usr/i386-buildroot-linux-uclibc/lib/
-isystem
/home/bernd/buildroot/br4_i386/output/host/usr/i386-buildroot-linux-uclibc/include
-isystem
/home/bernd/buildroot/br4_i386/output/host/usr/i386-buildroot-linux-uclibc/sys-include
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -O2
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fpic -mlong-double-80 -I. -I. -I../.././gcc
-I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc
-I../../../libgcc/../include -DUSE_TLS -o _gcov_ior_profiler.o -MT
_gcov_ior_profiler.o -MD -MP -MF _gcov_ior_profiler.dep -DL_gcov_ior_profiler
-c ../../../libgcc/libgcov-profiler.c
../../../libgcc/generic-morestack-thread.c:41:21: fatal error: pthread.h: No
such file or directory
#include <pthread.h>
^
compilation terminated.
../../../libgcc/shared-object.mk:14: recipe for target
'generic-morestack-thread.o' failed
make[3]: *** [generic-morestack-thread.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
'/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/build/i386-buildroot-linux-uclibc/libgcc'
Makefile:10153: recipe for target 'all-target-libgcc' failed
make[2]: *** [all-target-libgcc] Error 2
make[2]: Leaving directory
'/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/build'
Makefile:840: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory
'/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/build'
package/pkg-generic.mk:195: recipe for target
'/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/.stamp_built'
failed
make: ***
[/home/bernd/buildroot/br4_i386/output/build/host-gcc-final-4.9.3/.stamp_built]
Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-06 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 11:08 bugzilla at busybox.net [this message]
2016-03-06 12:51 ` [Buildroot] [Bug 8766] Compiling host-gcc-final-4.9.3 broken on i386 bugzilla at busybox.net
2016-03-06 12:55 ` 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@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