Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Simonov <sv@sw.ru>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
	gdb-patches@sourceware.org,        gdb@sourceware.org
Subject: Re: [commit] Rename STRINGIFY (Re: Macro conflict in gdb/opencl-lang.c)
Date: Wed, 02 Feb 2011 14:59:00 -0000	[thread overview]
Message-ID: <4D496CA5.9070800@sw.ru> (raw)
In-Reply-To: <20110202140722.GJ2384@adacore.com>

On 02/02/2011 05:07 PM, Joel Brobecker wrote:
>>> Macro STRINGIFY conflicts with
>>> mingw64 internal include:
>>
>> That's a bit unfortunate, such includes shouldn't really
>> intrude on the user namespace ...
>
> What I don't understand is why I am not seeing the problem...
> I've just successfully rebuilt GDB on x64 Windows, and the include
> in question does have the STRINGIFY macro.
>
>> ChangeLog:
>>
>> 	* opencl-lang.c (STRINGIFY): Rename to OCL_STRING.
>> 	(BUILD_OCL_VTYPES): Update.
>
> Thanks for taking care of the problem, though.
>
>

Looks like my mingw a bit old - mingw-w64-snapshot-20090419
The current one doesn't have a problem:
mingw-w64-v1.0-20101003/mingw-w64-headers/include/ChangeLog
2009-12-04  Jonathan Yong  <jon_y@users.sourceforge.net>

         * _mingw_mac.h (STRINGIFY): Rename to __MINGW64_STRINGIFY
         (__MINGW64_VERSION_STR): Use __MINGW64_STRINGIFY

Ulrich, thank you for fix.

Best regards
Vladimir Simonov


      reply	other threads:[~2011-02-02 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D483FE0.70700@sw.ru>
2011-02-02 13:50 ` Ulrich Weigand
2011-02-02 14:07   ` Joel Brobecker
2011-02-02 14:59     ` Vladimir Simonov [this message]

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=4D496CA5.9070800@sw.ru \
    --to=sv@sw.ru \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.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