From: Eli Zaretskii <eliz@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: andrewjmoreton@gmail.com, guile-devel@gnu.org
Subject: Re: Update 'uname' emulation on MS-Windows
Date: Sun, 24 Jul 2016 17:32:12 +0300 [thread overview]
Message-ID: <83poq3t8cz.fsf@gnu.org> (raw)
In-Reply-To: <878twsrrrh.fsf@pobox.com> (message from Andy Wingo on Sat, 23 Jul 2016 23:03:46 +0200)
> From: Andy Wingo <wingo@pobox.com>
> Cc: andrewjmoreton@gmail.com, guile-devel@gnu.org
> Date: Sat, 23 Jul 2016 23:03:46 +0200
>
> >> > Does the Mingw toolchain supply a suitable manifest automatically ?
> >>
> >> No. The manifest should be provided with Guile.
> >
> > Of course, singe Guile is mainly a library, any application that is
> > linked against libguile also needs such a manifest.
>
> Does the uname MinGW patch introduce a regression in any case that we
> care about?
No. On the contrary: where before Guile would only report correct OS
version up to and including XP, it now reports correct values also for
Vista, Windows 7, and Windows 8. Versions beyond that require the
manifest, and otherwise will be reported as 8.0.
Also, the modern CPU types are now supported, including 64-bit ones,
which were not reported at all before.
> Is it a user-visible change? If so an update to NEWS might be
> needed.
From my POV, this is a bugfix: APIs that were reporting inaccurate
values now report more accurate ones.
next prev parent reply other threads:[~2016-07-24 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 7:27 Update 'uname' emulation on MS-Windows Eli Zaretskii
2016-07-16 8:58 ` Andy Wingo
2016-07-16 10:33 ` Eli Zaretskii
2016-07-16 21:40 ` Andy Moreton
2016-07-17 2:37 ` Eli Zaretskii
2016-07-17 12:04 ` Eli Zaretskii
2016-07-23 21:03 ` Andy Wingo
2016-07-24 14:32 ` Eli Zaretskii [this message]
2016-07-24 17:04 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83poq3t8cz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).