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: Wed, 18 Mar 2009 11:15:42 +0100 [thread overview]
Message-ID: <20090318101542.GC20072@thorin> (raw)
In-Reply-To: <ca0f59980903162254me9f2ac7v8bef8f6070cea1c@mail.gmail.com>
On Tue, Mar 17, 2009 at 01:54:22PM +0800, Bean wrote:
> >
> > It seems you defined the mingw32 version of grub_millisleep unconditionally.
>
> Hi,
>
> Are you suggesting adding some test in configure.ac ? Although
> grub_millisleep for mingw32 uses Windows API Sleep, I guess it's safe
> to assume it's present.
I just meant that when __MINGW32__ is not defined, the function is implemented
twice:
> +#ifndef __MINGW32__
> void
> grub_millisleep (grub_uint32_t ms)
> {
> @@ -320,6 +321,7 @@ grub_millisleep (grub_uint32_t ms)
> ts.tv_nsec = (ms % 1000) * 1000000;
> nanosleep (&ts, NULL);
> }
> +#endif
>
> void
> grub_arch_sync_caches (void *address __attribute__ ((unused)),
> @@ -361,6 +363,12 @@ void sleep (int s)
> Sleep (s * 1000);
> }
>
> +void
> +grub_millisleep (grub_uint32_t ms)
> +{
> + Sleep (ms);
> +}
> +
why not put them together anyway? Like #ifdef __MINGW32__ ... #else ... #endif
--
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-18 10:15 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
2009-03-17 5:54 ` Bean
2009-03-18 10:15 ` Robert Millan [this message]
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=20090318101542.GC20072@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.