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] #44470: Please provide a newer GCC version
(MinGW Notification List)
----------------------------------------------------------------------
Message: 1
Date: Mon, 23 May 2022 15:08:27 +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-23 15:08
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-23 15:08 Updated by: eliz
Comment:
Reply To keith
Reply To eliz
Are we allowed to take ideas from what MinGW64 did in this case?
Presumably you mean by reading their header files? Sorry, but I consider that
to be a poisoned chalice, so I'd have to say "no". I'd be more inclined to
accept ideas gleaned from the (doxygen format) ReactOS reference documentation
— at least that offers something akin to a "chinese wall", and doesn't involve
directly reading header files, which we suspect may have been plagiarized from
Microsoft's copyrighted sources.
I don't think it matters where we take the idea for the implementation, ReactOS
is as good a source as any.
(My alternative suggestion would be that I describe in prose what MinGW64 did,
and you use that description to write the code. AFAIU, this works around the
copyright restriction, since ideas cannot be copyrighted. But it's an academic
issue now.)
---------------------------------------------------------------------
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: Mon, 23 May 2022 15:22:03 +0300
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #44470: Please provide a newer GCC
version
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8
#44470: Please provide a newer GCC version
Open Date: 2022-04-26 15:29
Last Update: 2022-05-23 15:22
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/44470
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44470
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-05-23 15:22 Updated by: eliz
Comment:
Reply To keith
Reply To eliz
The latest version of GCC, 9.2.0, available for MinGW development, was released
almost 2 years ago and last updated more than a year ago.
Would it be possible to provide a MinGW port of a newer GCC version, like 10 or
maybe even 11?
Given the will, anything may be possible, but who is going to develop, and
maintain it?
Since retiring from my day job, nearly nine years ago, I have had no real need
to use Windows for anything, beyond a desire to not see the MinGW.OSDN project,
and its associated user community, die. However, that community cannot
continue to depend on my solitary effort, indefinitely.
I see your point. Would you be willing to publish the procedure you were using
for building GCC, including the configuration options, the rationale for using
non-default options, and any notes and tricks that could be helpful for
building future versions of GCC for MinGW? Maybe someone else could step up,
if the bar was somewhat lower than starting from scratch.
I did attempt to build GCC-10.2.0, around a year ago — I got as far as
completing a GNU/Linux-hosted cross-compiler build, but ran into a brick wall,
when trying to use that, to create a crossed-native Windows-hosted build. I've
already posted regarding one issue arising. While that may not appear to be a
show stopping issue, (other than for those users who want Ada support), I've
since stumbled on to another, which is. When I compile any program — even a
trivial "hello world" — with my MinGW-GCC-10.2.0 cross-compiler, and
subsequently attempt to debug it, in GDB-9.2, on my Win7 virtual machine, I see:
{{{
Z:\> gdb foo.exe
GNU gdb (MinGW-GDB with Python 2.7.18) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
...
Reading symbols from foo.exe...
(gdb) start
Temporary breakpoint 1 at 0x4016b0: file foo.c, line ...
Starting program: Z:\foo.exe
Warning:
Cannot insert breakpoint 1.
Cannot access memory at address 0x4016a2
Command aborted.
}}}
From this point on, any attempt to step through the program, or to simply
continue execution, (unless I delete all pending breakpoints), is denied —
hardly useful for debugging. When the self-same program is compiled by my
MinGW-GCC-9.2.0 cross-compiler, I see no such problems with GDB, on the Win7 VM.
Could this be due to Binutils? Maybe GCC 10 requires a newer version of
Binutils than the one you have?
Does the program run normally when not debugged?
In any case, thanks for your efforts of maintaining MinGW for so many years.
---------------------------------------------------------------------
Ticket Status:
Reporter: eliz
Owner: (None)
Type: Feature Request
Status: Open
Priority: 5 - Medium
MileStone: (None)
Component: GCC
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
The latest version of GCC, 9.2.0, available for MinGW development, was released
almost 2 years ago and last updated more than a year ago.
Would it be possible to provide a MinGW port of a newer GCC version, like 10 or
maybe even 11?
Thanks in advance.
--
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/44470
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=44470
------------------------------
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 4
*******************************************
