From: Marco Trudel <mtrudel@gmx.ch>
To: gnustuff@thisiscool.com
Cc: tromey@redhat.com, keiths@redhat.com,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: jdwp build failure
Date: Thu, 22 Feb 2007 08:10:00 -0000 [thread overview]
Message-ID: <45DD4FC7.8060209@gmx.ch> (raw)
In-Reply-To: <HC86TPB86Z97WO32PUTQNDC3WKGZY.45dd01b9@parallels>
Mohan Embar wrote:
> Hi All,
>
>> Mohan> I haven't looked into this much, but if the Linux folks aren't
>> Mohan> having a problem with this, I'm suspecting a Win32 macro
>> Mohan> which is colliding with OUT. Just a guess, though.
>
>> It would be nice to know where this conflict comes from.
>> Sometimes a '#undef OUT' in win32.h can help...
>> But if we have to we can rename the field.
>
> I had already tried that, but it didn't work.
Works for me if I put it in the header.
I just took a look at the preprocessed output without the undef:
case JdwpConstants$StepDepth::OUT: becomes
case JdwpConstants$StepDepth:::
while others like
case JdwpConstants$StepDepth::StepDepth:
stay unchanged. What does that now mean? If "OUT" is used somewhere else
already, what's the proper action to do? Rename our new "OUT"? Find the
first "OUT"?
Marco
next prev parent reply other threads:[~2007-02-22 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 21:11 FYI: 2 patches for RH 4.1 branch Tom Tromey
2007-02-17 1:53 ` Mohan Embar
2007-02-17 8:31 ` Marco Trudel
2007-02-17 21:35 ` Marco Trudel
2007-02-17 23:08 ` Mohan Embar
2007-02-18 10:54 ` Marco Trudel
2007-02-19 13:10 ` Mohan Embar
2007-02-19 13:21 ` Marco Trudel
2007-02-21 12:46 ` jdwp build failure Marco Trudel
2007-02-21 18:05 ` Mohan Embar
2007-02-22 2:04 ` Tom Tromey
2007-02-22 2:37 ` Mohan Embar
2007-02-22 8:10 ` Marco Trudel [this message]
2007-02-22 8:12 Danny Smith
2007-02-22 8:21 ` Marco Trudel
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=45DD4FC7.8060209@gmx.ch \
--to=mtrudel@gmx.ch \
--cc=gnustuff@thisiscool.com \
--cc=java-patches@gcc.gnu.org \
--cc=keiths@redhat.com \
--cc=tromey@redhat.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).