public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/42271] os_defines.h:60:1: error: expected '{' before '_GLIBCXX_PSEUDO_VISIBILITY'
Date: Fri, 04 Dec 2009 18:01:00 -0000 [thread overview]
Message-ID: <20091204180048.31646.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42271-276@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from davek at gcc dot gnu dot org 2009-12-04 18:00 -------
I didn't anticipate any of the os-specific config headers trying to use the
namespace macros, since all the necessary defines and stuff are only half-way
through being set up, but I didn't imagine the possibility of wanting to import
some libc functions. I probably could have anticipated this if I'd done a bit
more grepping around, sorry.
JDA, I don't have headers and libs to test a hpux cross-compiler, could you
test the patch?
--
davek at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-12-04 18:00:47
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42271
next prev parent reply other threads:[~2009-12-04 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 3:47 [Bug bootstrap/42271] New: " danglin at gcc dot gnu dot org
2009-12-04 3:50 ` [Bug bootstrap/42271] " dave at hiauly1 dot hia dot nrc dot ca
2009-12-04 10:49 ` paolo dot carlini at oracle dot com
2009-12-04 17:30 ` davek at gcc dot gnu dot org
2009-12-04 17:59 ` davek at gcc dot gnu dot org
2009-12-04 18:01 ` davek at gcc dot gnu dot org [this message]
2009-12-04 18:22 ` dave at hiauly1 dot hia dot nrc dot ca
2009-12-04 18:23 ` davek at gcc dot gnu dot org
2009-12-04 23:39 ` dave at hiauly1 dot hia dot nrc dot ca
2009-12-05 2:28 ` davek at gcc dot gnu dot org
2009-12-05 6:14 ` davek at gcc dot gnu dot org
2009-12-05 6:16 ` davek at gcc dot gnu dot org
2010-03-23 1:56 ` davek 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=20091204180048.31646.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).