public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dan at danny dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55344] New: Cross compiling for alpha-linux fails because <signal.h> doesn't exist
Date: Thu, 15 Nov 2012 18:01:00 -0000 [thread overview]
Message-ID: <bug-55344-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55344
Bug #: 55344
Summary: Cross compiling for alpha-linux fails because
<signal.h> doesn't exist
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dan@danny.cz
Created attachment 28702
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28702
fix cross build
Cross compiling libgcc for alpha-linux fails because <signal.h> included from
libgcc/config/alpha/linux-unwind.h doesn't exist
/builddir/build/BUILD/gcc-4.7.2-20121114-aarch64/alpha-linux-gnu/./gcc/xgcc
-B/builddir/build/BUILD/gcc-4.7.2-20121114-aarch64/alpha-linux-gnu/./gcc/
-B/usr/alpha-linux-gnu/bin/ -B/usr/alpha-linux-gnu/lib/ -isystem
/usr/alpha-linux-gnu/include -isystem /usr/alpha-linux-gnu/sys-include -g
-O2 -mieee -O2 -g -O2 -mieee -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mieee
-g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fPIC
-mieee -I. -I. -I../.././gcc -I../../../gcc-4.7.2-20121114-aarch64/libgcc
-I../../../gcc-4.7.2-20121114-aarch64/libgcc/.
-I../../../gcc-4.7.2-20121114-aarch64/libgcc/../gcc
-I../../../gcc-4.7.2-20121114-aarch64/libgcc/../include -DHAVE_CC_TLS -o
unwind-c.o -MT unwind-c.o -MD -MP -MF unwind-c.dep -fexceptions -c
../../../gcc-4.7.2-20121114-aarch64/libgcc/unwind-c.c
In file included from
../../../gcc-4.7.2-20121114-aarch64/libgcc/unwind-dw2.c:376:0:
./md-unwind-support.h:28:20: fatal error: signal.h: No such file or directory
compilation terminated.
next reply other threads:[~2012-11-15 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:01 dan at danny dot cz [this message]
2012-12-09 1:09 ` [Bug target/55344] " pinskia at gcc dot gnu.org
2012-12-09 14:04 ` ubizjak at gmail dot com
2012-12-09 18:16 ` uros at gcc dot gnu.org
2012-12-09 18:21 ` uros at gcc dot gnu.org
2012-12-09 18:24 ` ubizjak at gmail dot com
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-55344-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).