Does libscotch.dll from scotch-int64 and mingw-scotch-int64 packages really provide int64 interface?

[ChessMastery]

Description / Steps to reproduce the issue

I downloaded mingw-w64-x86_64-mumps package, and used it correctly with libscotch.dll from mingw-w64-x86_64-scotch package. Then I downloaded mingw-w64-x86_64-scotch-int64 and mingw-w64-ucrt-x86_64-scotch-int64, and these packages also provide libscotch.dll, but when I replace old libscotch.dll with the one provided by these packages, mumps still works correctly. From the other hand, when I try to link "int64" libscotch.dll to 64-bit integer mumps, it return error -52 that means it thinks 32-bit scotch was provided. How should I check which functions does libscotch.dll export and are they 32-bit-int or 64-bit-int?

Expected behavior

Expected behaviour: I guess mumps-int32 should not work fine with scotch-int64.

Actual behavior

Actual behaviour: mumps-int32 works fine with libscotch.dll obtained from scotch-in64 and ucrt-scotch-int64 packages.

Verification

• [X] I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

Windows 10 Pro 22H2

MINGW environments affected

• [X] MINGW64
• [ ] MINGW32
• [X] UCRT64
• [ ] CLANG64
• [ ] CLANGARM64

Are you willing to submit a PR?

No response

[Biswa96]

@3rav could you look into this issue please?