From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH 0/2] Disable functionality that doesn't work on MINGW32
Date: Thu, 22 Sep 2011 00:02:57 +0200 [thread overview]
Message-ID: <4E7A5F11.4060600@gmail.com> (raw)
In-Reply-To: <4E7A574B.7040602@dell.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
On 21.09.2011 23:29, Mario Limonciello wrote:
> The following two patches are for disabling some specifics that will
> not work on MINGW32.
>
> Vladimir explicitly expressed disinterest in going the route of #undef
> GRUB_UTIL, but it seems to be the most appropriate method in the first
> patch to me because MINGW32 does not support ttys and won't ever.
>
GRUB_UTIL means that we run under an OS and use it. While Windows is a
low-quality one, it's still one, so GRUB_UTIL must be defined. Correct
way to dial with this issue is to add a windows equivalent of this code
(requesting password from user).
> The second patch just matches other code, since there is no
> grub_util_get_fd_sectors defined on MINGW32. This will at least get
> the file compiling with potentially broken functionality, which I see
> as an improvement over not compiling and no functionality.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2011-09-21 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 21:29 [PATCH 0/2] Disable functionality that doesn't work on MINGW32 Mario Limonciello
2011-09-21 22:02 ` 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=4E7A5F11.4060600@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.