public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55344] Cross compiling for alpha-linux fails because <signal.h> doesn't exist
Date: Sun, 09 Dec 2012 14:04:00 -0000 [thread overview]
Message-ID: <bug-55344-4-lhLKmntKGp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55344-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55344
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ubizjak at gmail dot com
Target Milestone|--- |4.7.3
--- Comment #2 from Uros Bizjak <ubizjak at gmail dot com> 2012-12-09 14:04:26 UTC ---
I am testing following trivial patch:
--cut here--
Index: config/alpha/linux-unwind.h
===================================================================
--- config/alpha/linux-unwind.h (revision 194329)
+++ config/alpha/linux-unwind.h (working copy)
@@ -22,6 +22,7 @@
see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
<http://www.gnu.org/licenses/>. */
+#ifndef inhibit_libc
/* Do code reading to identify a signal frame, and set the frame
state data appropriately. See unwind-dw2.c for the structs. */
@@ -97,3 +98,4 @@
|| pc[1] == 0x201f015f)) /* lda $0,NR_rt_sigreturn */
_Unwind_SetSignalFrame (context, 1);
}
+#endif
--cut here--
next prev parent reply other threads:[~2012-12-09 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:01 [Bug target/55344] New: " dan at danny dot cz
2012-12-09 1:09 ` [Bug target/55344] " pinskia at gcc dot gnu.org
2012-12-09 14:04 ` ubizjak at gmail dot com [this message]
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-lhLKmntKGp@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).