public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/40702] lto-elf.c fails to compile on Solaris
Date: Mon, 05 Oct 2009 14:05:00 -0000 [thread overview]
Message-ID: <20091005140510.18795.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40702-279@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from ro at techfak dot uni-bielefeld dot de 2009-10-05 14:05 -------
Subject: Re: lto-elf.c fails to compile on Solaris
> ------- Comment #3 from rguenth at gcc dot gnu dot org 2009-10-05 13:13 -------
> That's weird. So is this a libelf bug after all or can we somehow workaround
> it
> in gcc?
I think it's a libelf bug. I'll report it upstream. In addition, I'll
check if STDC_0_IN_SYSTEM_HEADERS is still necessary on Solaris 2.
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40702
next prev parent reply other threads:[~2009-10-05 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 19:10 [Bug bootstrap/40702] New: " ro at gcc dot gnu dot org
2009-10-03 22:12 ` [Bug lto/40702] " rguenth at gcc dot gnu dot org
2009-10-05 12:56 ` ro at techfak dot uni-bielefeld dot de
2009-10-05 13:13 ` rguenth at gcc dot gnu dot org
2009-10-05 14:05 ` ro at techfak dot uni-bielefeld dot de [this message]
2010-04-23 14:34 ` rguenth at gcc dot gnu dot org
2010-04-23 18:09 ` ebotcazou at gcc dot gnu dot org
2010-04-28 11:16 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-04-28 11:55 ` rguenth at gcc dot gnu dot org
2010-04-28 13:02 ` hubicka at gcc dot gnu dot org
2010-04-28 14:41 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-06-03 13:47 ` rguenth at gcc dot gnu dot org
2010-06-04 15:21 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-24 16:24 ` rguenth at gcc dot gnu dot org
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=20091005140510.18795.qmail@sourceware.org \
--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).