[patch bfd]: Add further support for x86_64 mingw

Kai Tietz Kai.Tietz@onevision.com
Wed Jan 23 13:14:00 GMT 2008


Brian Dessent <brian@dessent.net> wrote on 22.01.2008 16:53:49:

> Kai Tietz wrote:
> 
> > AFAIK doesn't cygwin define _WIN32. I checked current gcc sources and
> > didn't saw it for cgywin, just for mingw32. The __MSVCRT__ would be an
> > alternative, for sure. But isn't the macro _WIN32 just the API we use?
> 
> Correct, Cygwin does not normally define _WIN32 but if you #include
> <windows.h> it gets defined there too... it's not a common scenario
> since the goal of Cygwin is not to use Windowsisms, but you can still do
> it if you need access to something in the w32api and there's no POSIX
> analog.

Upps your are right 8) I missed this. So I will replace the #ifdef _WIN32 
by #ifdef __MSVCRT__. Is this fine?

I attached the updated patch files.

 Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gas_x86_64_mingw.txt
URL: <https://sourceware.org/pipermail/binutils/attachments/20080123/80792531/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: binutils_x86_64_mingw.txt
URL: <https://sourceware.org/pipermail/binutils/attachments/20080123/80792531/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bfd_x86_64_mingw.txt
URL: <https://sourceware.org/pipermail/binutils/attachments/20080123/80792531/attachment-0002.txt>


More information about the Binutils mailing list