在 2022-04-28 23:55, Corinna Vinschen 写道:
But then again, this seems to be a bug in the w32api import libs,
rather than a problem with the toolchain, no?
Yes; and similar issues did happen some times before, such as in these commits:
* 68d0e7d551d2e2a5b8a15bdca3f8d15fc097ed01
* 65042f860
Hi Corinna,
Corinna Vinschen wrote:
On Apr 28 17:34, Corinna Vinschen wrote:
Hi Christian,
On Apr 28 17:24, Christian Franke wrote:
For some unknown reason, certain functions from advapi32.dll are now also
exported by the kernel32.dll of recent Windows versions. To provide backward
compatibil
On Apr 28 17:34, Corinna Vinschen wrote:
> Hi Christian,
>
> On Apr 28 17:24, Christian Franke wrote:
> > For some unknown reason, certain functions from advapi32.dll are now also
> > exported by the kernel32.dll of recent Windows versions. To provide backward
> > compatibility, -ladvapi32 must oc
Hi Christian,
On Apr 28 17:24, Christian Franke wrote:
> For some unknown reason, certain functions from advapi32.dll are now also
> exported by the kernel32.dll of recent Windows versions. To provide backward
> compatibility, -ladvapi32 must occur before -lkernel32 in the linker
> command, but th
For some unknown reason, certain functions from advapi32.dll are now
also exported by the kernel32.dll of recent Windows versions. To provide
backward compatibility, -ladvapi32 must occur before -lkernel32 in the
linker command, but this is not the case by default:
Testcase with current packag
