From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Use _W64 to detect MinGW W64-32 instead of _FILE_OFFSET_BITS
Date: Sat, 18 Jan 2014 16:56:42 +0100 [thread overview]
Message-ID: <52DAA43A.20005@gmail.com> (raw)
In-Reply-To: <20140118195352.1f1b49e1@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On 18.01.2014 16:53, Andrey Borzenkov wrote:
> В Sat, 18 Jan 2014 16:22:21 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
>
>> On 14.01.2014 04:05, Andrey Borzenkov wrote:
>>> +/* 32 bit on Mingw-w64 already redefines them if _FILE_OFFSET_BITS=64 */
>> Do you mean 64-bit ?
>>
>
> No, I mean exactly 32 bit. 'Mingw w64" is project (toolchain) name; it
> can produce both 32 bit and 64 bit programs. 64 bit is already covered
> by __MINGW64__, but in 32 bit case we need to differentiate between
> native MinGW and Mingw w64 building for 32 bit.
>
I see.
Go ahead.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]
prev parent reply other threads:[~2014-01-18 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 10:10 [PATCH] fix 32 bit compilation on MinGW-w64 Andrey Borzenkov
2014-01-07 13:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-14 3:05 ` [PATCH] Use _W64 to detect MinGW W64-32 instead of _FILE_OFFSET_BITS Andrey Borzenkov
2014-01-18 15:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-18 15:53 ` Andrey Borzenkov
2014-01-18 15:56 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=52DAA43A.20005@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.