bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Roger Pack <rogerdpack@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: gettimeofday.c windows version?
Date: Fri, 23 Dec 2022 01:38:01 -0700	[thread overview]
Message-ID: <CAPfeOnvpX3i0CCgzSEksSrDvcTG5zLHfW55AAWZU4xvtbZoXTw@mail.gmail.com> (raw)
In-Reply-To: <2153083.vXnMlVU4IS@nimes>

[-- Attachment #1: Type: text/plain, Size: 3081 bytes --]

On Sun, Dec 11, 2022 at 7:22 AM Bruno Haible <bruno@clisp.org> wrote:

> Roger Pack wrote:
> > I received some complaints saying in mingw it was"requiring windows 8"
> for
> > a certain library.
> >
> > "Entry point not found, GetSystemTimePreciseAsFileTime could not be
> located
> > in the dynamic link library KERNEL32.dll".
>
> Indeed, according to <
> https://learn.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getsystemtimepreciseasfiletime
> >
> the function GetSystemTimePreciseAsFileTime is not present in Windows 7 and
> older.
>
> Looking at the table at
> <https://en.wikipedia.org/wiki/Microsoft_Windows#Timeline_of_releases> I
> see
> that Windows 7 is out of "extended support" already for more than 2 years.
> That means, users with such machines (connected to the internet) live very
> dangerously.
>
> Eli: What are the current support statements of Emacs regarding Windows
> XP/Vista/7 ?
> And should Gnulib declare that the minimum supported version of Windows
> is Windows 8?
>
> > Perhaps the following patch?  Thanks! :)
> >
> > diff --git a/lib/gettimeofday.c b/lib/gettimeofday.c
> > index 36c7920af..428cc4f30 100644
> > --- a/lib/gettimeofday.c
> > +++ b/lib/gettimeofday.c
> > @@ -35,7 +35,7 @@
> >  # undef LoadLibrary
> >  # define LoadLibrary LoadLibraryA
> >
> > -# if !(_WIN32_WINNT >= _WIN32_WINNT_WIN8)
> > +# if (_WIN32_WINNT >= _WIN32_WINNT_WIN8)
> >
> >  /* Avoid warnings from gcc -Wcast-function-type.  */
> >  #  define GetProcAddress \
> >
>
> Nope, this patch is not right.
>
> > "Entry point not found, GetSystemTimePreciseAsFileTime could not be
> located
> > in the dynamic link library KERNEL32.dll".
>
> It looks like some code links directly to GetSystemTimePreciseAsFileTime,
> and
> your user is running it under Windows 7 or older.
>
> Which object file is it that links to GetSystemTimePreciseAsFileTime?
>  - If it's not gettimeofday.c, it's not in Gnulib's responsibility.
>  - If it is gettimeofday.c, this file must have been compiled with a
>    _WIN32_WINNT value >= _WIN32_WINNT_WIN8. You need to look in your
>    build files where this value come from. Maybe it is even the default
>    with your compiler version; if that version is new enough, that would
>    make sense.
>

OK it appears newer mingw have a default target of windows 10 for some
reason.  gnutls embedded in this case:
$ x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../..   -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=0  -mtune=generic -O3 -MT gettimeofday.o -MD -MP -MF
$depbase.Tpo -c -o - -dM -E gettimeofday.c | grep WIN32_WINNT
#define _WIN32_WINNT 0xa00
https://www.mail-archive.com/mingw-w64-public@lists.sourceforge.net/msg18212.html

Maybe instead it could always call initialize and "prefer"
GetSystemTimePreciseAsFileTime, then be compatible with < windows 8 without
having to manually set _WIN32_WINNT.
Basically everything using Gnulib gettimeofday + mingw today might
"accidentally" lose windows 7 compat without realizing it.  Though I guess
you could call that Mingw's fault, it was a bit confusing.
Thanks, Merry Christmas!

[-- Attachment #2: Type: text/html, Size: 4255 bytes --]

  parent reply	other threads:[~2022-12-23  8:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11  6:01 gettimeofday.c windows version? Roger Pack
2022-12-11  7:05 ` Roger Pack
2022-12-11 14:22 ` Bruno Haible
2022-12-11 15:09   ` Eli Zaretskii
2022-12-11 16:20     ` Bruno Haible
2022-12-11 16:56       ` Eli Zaretskii
2022-12-11 17:25         ` Eli Zaretskii
2022-12-11 18:25           ` Bruno Haible
2022-12-11 18:55             ` Eli Zaretskii
2022-12-12  7:17               ` Paul Eggert
2022-12-12 12:19                 ` Bruno Haible
2022-12-12 13:06                 ` Eli Zaretskii
2022-12-12 14:25                   ` Bruno Haible
2022-12-12 14:40                     ` Eli Zaretskii
2022-12-12 19:44                       ` Paul Eggert
2022-12-12 20:37                         ` Eli Zaretskii
2022-12-16 23:35                           ` Paul Eggert
2022-12-17  8:09                             ` Eli Zaretskii
2022-12-12 19:14                     ` Gisle Vanem
2022-12-23  8:38   ` Roger Pack [this message]
2022-12-23  8:46     ` Eli Zaretskii
2022-12-23 23:47     ` Paul Eggert
2022-12-24  6:46       ` Eli Zaretskii
2022-12-24  7:42         ` Paul Eggert
2022-12-24  8:34           ` Eli Zaretskii

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPfeOnvpX3i0CCgzSEksSrDvcTG5zLHfW55AAWZU4xvtbZoXTw@mail.gmail.com \
    --to=rogerdpack@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eliz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).