bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rogerdpack@gmail.com, bruno@clisp.org, bug-gnulib@gnu.org
Subject: Re: gettimeofday.c windows version?
Date: Sat, 24 Dec 2022 10:34:31 +0200	[thread overview]
Message-ID: <83edsp5hew.fsf@gnu.org> (raw)
In-Reply-To: <72b0a1fa-e07f-224d-4060-15e0afc10296@cs.ucla.edu> (message from Paul Eggert on Fri, 23 Dec 2022 23:42:52 -0800)

> Date: Fri, 23 Dec 2022 23:42:52 -0800
> Cc: rogerdpack@gmail.com, bruno@clisp.org, bug-gnulib@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> On 12/23/22 22:46, Eli Zaretskii wrote:
> > We do this only for mingw.org's MinGW, not for MinGW64 (where we don't
> > change the default value).
> 
> Oh. How about if we do it for MinGW64 too? Wouldn't that support 64-bit 
> Emacs builds on obsolete MS-Windows platforms? Not being an MS-Windows 
> expert I'm hesitant to propose an exact patch, but the general idea 
> should work.

It's AFAIK meaningless to do that for MinGW64, since they dropped
support of all versions of Windows older than 8, and I hear they will
drop Windows 8 as well soon (or already did?).

> Another option would be to say that if you want to run Emacs on 
> MS-Windows no longer supported by Microsoft, you need to do a 32-bit build.

That is indeed the best alternative, since it is being constantly
tested (by yours truly).


      reply	other threads:[~2022-12-24  8:35 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
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 [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

  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=83edsp5hew.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=rogerdpack@gmail.com \
    /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).