From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] patch to compile grub2 in msys/mingw environment
Date: Sun, 15 Mar 2009 16:40:02 +0100 [thread overview]
Message-ID: <20090315154002.GC24554@thorin> (raw)
In-Reply-To: <ca0f59980903141227x2c6172g47a2f712af563cbc@mail.gmail.com>
On Sun, Mar 15, 2009 at 03:27:05AM +0800, Bean wrote:
> Hi,
>
> There are three issue related to msys/mingw environment.
>
> 1, no nanosleep in mingw, although, the windows API Sleep support millisecond.
>
> 2, Use stat on device like //./PHYSICALDRIVE0 would fail. It should
> use utility function grub_util_get_disk_size in read_device_map.
>
> 3, The ln command in msys can't handle symbol link properly, which
> causes AC_CONFIG_LINKS to fail. This patch add new test
> grub_CHECK_LINK_DIR, which is used to decide whether to call
> AC_CONFIG_LINKS or copy directory itself.
>
> 2009-03-14 Bean <bean123ch@gmail.com>
>
> * util/hostdisk.c (read_device_map): Use grub_util_get_disk_size to
> instead of stat in mingw environment.
>
> * util/misc.c (grub_millisleep): New function in environment.
>
> * aclocal.m4 (grub_CHECK_LINK_DIR): New function.
>
> * configure.ac: Use grub_CHECK_LINK_DIR to determine whether to use
> AC_CONFIG_LINKS.
It seems you defined the mingw32 version of grub_millisleep unconditionally.
Btw, would be nice if you could send patches as inline attachments, without
the base64 encoding. Then I'd have been able to reply using the patch as
context.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-03-15 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 19:27 [PATCH] patch to compile grub2 in msys/mingw environment Bean
2009-03-15 15:40 ` Robert Millan [this message]
2009-03-17 5:54 ` Bean
2009-03-18 10:15 ` Robert Millan
2009-03-18 13:43 ` Bean
2009-03-21 7:48 ` Bean
2009-03-21 17:51 ` Robert Millan
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=20090315154002.GC24554@thorin \
--to=rmh@aybabtu.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.