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] #44471: Wrong prototype of IsProcessInJob
(MinGW Notification List)
2. [mingw] #44471: Wrong prototype of IsProcessInJob
(MinGW Notification List)
3. [mingw] #44502: mingw-get-setup only offer old compiler
version (MinGW Notification List)
4. [mingw] #44502: mingw-get-setup only offer old compiler
version - CLOSED user error (MinGW Notification List)
----------------------------------------------------------------------
Message: 1
Date: Wed, 04 May 2022 08:42:18 +0300
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 15:42
Last Update: 2022-05-04 08:42
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-04 08:42 Updated by: eliz
Comment:
Reply To keith
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.
Yes, the change I propose definitely solved linking errors in a program where I
needed this function.
---------------------------------------------------------------------
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: 2
Date: Wed, 04 May 2022 08:42:59 +0300
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 15:42
Last Update: 2022-05-04 08:42
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-04 08:42 Updated by: eliz
Comment:
Reply To keith
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.
Are we allowed to take ideas from what MinGW64 did in this case?
---------------------------------------------------------------------
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: 3
Date: Wed, 04 May 2022 03:41:37 -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-04 03:41
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-04 03:41 Updated by: guyr
Comment:
Keith, thank you for your quick and thorough response. You are correct: I
apparently downloaded mingw-get-setup from SourceForge, but then followed the
link listed there to OSDN.net and continued my installation. Just now, I
removed that installation, and started over again after downloading
mingw-get-setup from OSDN.net. As you correctly describe, now the 9.2.0
compiler version is listed.
I'm just a developer using the MinGW tools, so I'm not privy to the long
history of MinGW and MinGW-w64. I'm not a lawyer. However, a little Googling
informed me that MinGW-w64 forked from MinGW in 2005, while the MINGW trademark
was granted in 2014. I'm guessing the MinGW-w64 camp would claim prior works.
I appreciate your help and pointing me in the right direction. I'll close this
ticket as user error if I'm able.
---------------------------------------------------------------------
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: 4
Date: Wed, 04 May 2022 03:43:03 -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 - CLOSED user error
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44502: mingw-get-setup only offer old compiler version - CLOSED user error
Open Date: 2022-05-02 23:42
Last Update: 2022-05-04 03:43
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-04 03:43 Updated by: guyr
* Status Update from Open to Closed
* Resolution Update from None to Invalid
* Summary Updated
---------------------------------------------------------------------
Ticket Status:
Reporter: guyr
Owner: (None)
Type: Issues
Status: Closed
Priority: 5 - Medium
MileStone: (None)
Component: GCC
Severity: 5 - Medium
Resolution: Invalid
---------------------------------------------------------------------
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
------------------------------
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 2
*******************************************
