From: Florian Weimer <fw@deneb.enyo.de>
To: "Jing Lee" <jlee@kang.bondnet.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: GCC compiling problem on solaris intel machine
Date: Wed, 27 Nov 2002 00:28:00 -0000 [thread overview]
Message-ID: <87lm3f1knv.fsf@deneb.enyo.de> (raw)
In-Reply-To: <PCEHJELEKPHKCDMOIMPMOEIICAAA.jlee@bondnet.com> ("Jing Lee"'s message of "Mon, 25 Nov 2002 17:48:35 -0500")
"Jing Lee" <jlee@kang.bondnet.com> writes:
> sun/misc/SoftCacheProxyForward.h:5: parse error before numeric constant
> #ifndef __sun_misc_ResourceProxyForward_H
> #define __sun_misc_ResourceProxyForward_H
>
> namespace sun
> {
You are compiling this on Solaris, right?
"sun" is probably a predefined preprocessor macro, so after
preprocessing your code becomes:
| namespace 1
| {
I'm sorry, I don't know how you can get rid of the "sun" macro without
disturbing the header files.
next prev parent reply other threads:[~2002-11-27 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 6:06 Jing Lee
2002-11-27 0:28 ` Florian Weimer [this message]
2002-11-27 6:33 ` Eljay Love-Jensen
2002-11-27 15:09 ` Florian Weimer
2002-12-02 5:45 ` Eljay Love-Jensen
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=87lm3f1knv.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jlee@kang.bondnet.com \
/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).