Send MinGW-Notify mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."
Please do not reply to this notification; the sender address is unable to
accept incoming e-mail. If you wish to unsubscribe you can do so at
https://lists.osdn.me/mailman/listinfo/mingw-notify.
Today's Topics:
1. [mingw] #44502: mingw-get-setup only offer old compiler
version (MinGW Notification List)
2. [mingw] #44502: mingw-get-setup only offer old compiler
version (MinGW Notification List)
3. [mingw] #44471: Wrong prototype of IsProcessInJob
(MinGW Notification List)
4. [mingw] #44471: Wrong prototype of IsProcessInJob
(MinGW Notification List)
----------------------------------------------------------------------
Message: 1
Date: Mon, 02 May 2022 23:42:20 -0400
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #44502: mingw-get-setup only offer old
compiler version
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44502: mingw-get-setup only offer old compiler version
Open Date: 2022-05-02 23:42
Last Update: 2022-05-02 23:42
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/44502
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44502
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-05-02 23:42 Updated by: guyr
* New Ticket "mingw-get-setup only offer old compiler version" created
---------------------------------------------------------------------
Ticket Status:
Reporter: guyr
Owner: (None)
Type: Issues
Status: Open
Priority: 5 - Medium
MileStone: (None)
Component: GCC
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
I installed using the provided mingw-get-setup. The setup succeeded, but only
offered GCC 6.3.0, even though this site claims 9.2.0 is available. I also
have mingw-w64 installed on this computer under msys2 64-bit, in a completely
separate directory. After setup completed, I started the msys environment
using MinGW\msys\1.0\msys.bat. From there, I attempted to update using packman
-Syu, which produces the following:
$ pacman -Syu
:: Synchronizing package databases...
mingw32
mingw64
ucrt64
clang64
msys
msys is up to date mingw64 is up to date clang64 is up to date ucrt64 is up to
date mingw32 is up to date:: Starting co
re system upgrade...
warning: terminate other MSYS2 programs before proceeding
resolving dependencies...
looking for conflicting packages...
Packages (3) filesystem-2022.01-4 mintty-1~3.6.0-1 pacman-6.0.1-14
Total Download Size: 6.37 MiB
Total Installed Size: 34.75 MiB
Net Upgrade Size: 0.20 MiB
:: Proceed with installation? [Y/n] n
Looks like there is a common pacman database, and this MinGW msys environment
is seeing the packages installed in the other environment.
At any rate, I'd like to get the newer GCC compiler in this MinGW environment.
Apparently this cannot be done via either mingw-get-setup or via pacman?
Thanks.
--
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN
Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/mingw/ticket/44502
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44502
------------------------------
Message: 2
Date: Tue, 03 May 2022 20:13:05 +0100
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #44502: mingw-get-setup only offer old
compiler version
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44502: mingw-get-setup only offer old compiler version
Open Date: 2022-05-03 04:42
Last Update: 2022-05-03 20:13
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/44502
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44502
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-05-03 20:13 Updated by: keith
Comment:
There are several issues here:
The mingw-w64 and MSYS2 projects are not, in any way, affiliated with MinGW.
Neither project is authorized to distribute MinGW products; any product which
they distribute, and which is described as "mingw", (or includes "mingw" within
its name), represents a trademark infringement. We do not support any such
illegitimately distributed product.
Pacman is the Arch Linux installer. While the MSYS2 project may have adopted a
port, as its installer, there is no legitimate MinGW product which it is able
to install. Once again, we do not support any such installation.
As a point of clarification, mingw-get-setup.exe exists for one purpose, and
one purpose only; that purpose is to install mingw-get — the MinGW installer
suite — and nothing else. mingw-get-setup.exe does not offer to install any
version of GCC; that is the province of mingw-get itself, after it has been
installed by mingw-get-setup.exe.
The bulk of the information, which you have provided, is completely unrelated
to any legitimate MinGW product. That the illegitimate products are visible
from within your legitimate MinGW environment is a consequence of how you have
configured your installation — likely you have included the bogus products
within the PATH, which you have made visible when running the legitimate MinGW
tools. Beyond this tip, I will offer no further advice in respect of
unsupported products.
With that said, the only issue you have raised, which is actually of concern
here, is:
I installed using the provided mingw-get-setup. The setup succeeded, but only
offered GCC 6.3.0, even though this site claims 9.2.0 is available.
You don't give me enough information, to help me diagnose your issue, but your
assertion is not borne out by evidence from my own Win7 installation:
$ mingw-get --version
mingw-get version 0.6.4
Copyright (C) 2009-2013, 2017, 2020, 2022, MinGW.OSDN Project
This is free software; see the product documentation, or source code,
for copying and redistribution conditions. There is NO WARRANTY; not
even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY
PARTICULAR PURPOSE.
keith@acer-laptop ~
$ mingw-get list mingw32-gcc-bin
Package: mingw32-gcc Subsystem: mingw32
Component: bin
Installed Version: gcc-core-9.2.0-2-mingw32-bin.tar.xz
Repository Version: gcc-core-9.2.0-2-mingw32-bin.tar.xz
The GNU C Compiler
------------------
This package provides the MinGW implementation of the GNU C language
compiler; this includes the C preprocessor, and the common back end
processors which are necessary to support all other language compilers
in the GNU Compiler Collection.
This is a required component of the MinGW Compiler Suite.
---------------------------------------------------------------------
Ticket Status:
Reporter: guyr
Owner: (None)
Type: Issues
Status: Open
Priority: 5 - Medium
MileStone: (None)
Component: GCC
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
I installed using the provided mingw-get-setup. The setup succeeded, but only
offered GCC 6.3.0, even though this site claims 9.2.0 is available. I also
have mingw-w64 installed on this computer under msys2 64-bit, in a completely
separate directory. After setup completed, I started the msys environment
using MinGW\msys\1.0\msys.bat. From there, I attempted to update using packman
-Syu, which produces the following:
$ pacman -Syu
:: Synchronizing package databases...
mingw32
mingw64
ucrt64
clang64
msys
msys is up to date mingw64 is up to date clang64 is up to date ucrt64 is up to
date mingw32 is up to date:: Starting co
re system upgrade...
warning: terminate other MSYS2 programs before proceeding
resolving dependencies...
looking for conflicting packages...
Packages (3) filesystem-2022.01-4 mintty-1~3.6.0-1 pacman-6.0.1-14
Total Download Size: 6.37 MiB
Total Installed Size: 34.75 MiB
Net Upgrade Size: 0.20 MiB
:: Proceed with installation? [Y/n] n
Looks like there is a common pacman database, and this MinGW msys environment
is seeing the packages installed in the other environment.
At any rate, I'd like to get the newer GCC compiler in this MinGW environment.
Apparently this cannot be done via either mingw-get-setup or via pacman?
Thanks.
--
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN
Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/mingw/ticket/44502
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44502
------------------------------
Message: 3
Date: Tue, 03 May 2022 21:48:51 +0100
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #44471: Wrong prototype of
IsProcessInJob
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44471: Wrong prototype of IsProcessInJob
Open Date: 2022-04-26 13:42
Last Update: 2022-05-03 21:48
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/44471
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44471
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-05-03 21:48 Updated by: keith
Comment:
Reply To eliz
The prototype of IsProcessInJob, as it is provided by winbase.h in the w32api
MinGW package seems to be incorrect:
WINBASEAPI BOOL IsProcessInJob (HANDLE, HANDLE, PBOOL);
I think it should instead be this:
WINBASEAPI BOOL WINAPI IsProcessInJob (HANDLE, HANDLE, PBOOL);
I found this because the existing prototype causes link error, since the linker
is looking for the wrong symbol in the libraries.
I suspect that you are correct. Microsoft's (woeful) documentation neither
supports, nor refutes your conjecture, but if your proposed prototype
adjustment both resolves the linking issue, and exhibits correct run-time
behaviour, that would seem to be sufficient justification for making the change.
---------------------------------------------------------------------
Ticket Status:
Reporter: eliz
Owner: (None)
Type: Issues
Status: Open
Priority: 5 - Medium
MileStone: (None)
Component: WSL
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
The prototype of IsProcessInJob, as it is provided by winbase.h in the w32api
MinGW package seems to be incorrect:
WINBASEAPI BOOL IsProcessInJob (HANDLE, HANDLE, PBOOL);
I think it should instead be this:
WINBASEAPI BOOL WINAPI IsProcessInJob (HANDLE, HANDLE, PBOOL);
I found this because the existing prototype causes link error, since the linker
is looking for the wrong symbol in the libraries.
--
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN
Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/mingw/ticket/44471
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44471
------------------------------
Message: 4
Date: Tue, 03 May 2022 22:35:52 +0100
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #44471: Wrong prototype of
IsProcessInJob
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44471: Wrong prototype of IsProcessInJob
Open Date: 2022-04-26 13:42
Last Update: 2022-05-03 22:35
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/44471
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44471
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-05-03 22:35 Updated by: keith
Comment:
In winbase.h I also see one other declaration, which appears to be similarly
malformed:
$ hg grep WINBASEAPI | grep -v WINAPI
... snip ...
w32api/include/winbase.h:WINBASEAPI HLOCAL LocalDiscard (HLOCAL);
w32api/include/winbase.h:WINBASEAPI BOOL IsProcessInJob (HANDLE, HANDLE, PBOOL);
Although the declaration of LocalDiscard here has every appearance of being
similarly malformed, the issue is different. Microsoft's documentation, in
this case, suggests that LocalDiscard should be defined as a macro, (but offers
no hint as to how it should be defined). Indeed, there does not appear to be
any symbol, exported from kernel32.dll, which could possibly resolve any
reference to LocalDiscard.
I have no idea how to fix this.
---------------------------------------------------------------------
Ticket Status:
Reporter: eliz
Owner: (None)
Type: Issues
Status: Open
Priority: 5 - Medium
MileStone: (None)
Component: WSL
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
The prototype of IsProcessInJob, as it is provided by winbase.h in the w32api
MinGW package seems to be incorrect:
WINBASEAPI BOOL IsProcessInJob (HANDLE, HANDLE, PBOOL);
I think it should instead be this:
WINBASEAPI BOOL WINAPI IsProcessInJob (HANDLE, HANDLE, PBOOL);
I found this because the existing prototype causes link error, since the linker
is looking for the wrong symbol in the libraries.
--
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN
Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/mingw/ticket/44471
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44471
------------------------------
Subject: Digest Footer
_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify
------------------------------
End of MinGW-Notify Digest, Vol 52, Issue 1
*******************************************
