Re: [Plplot-devel] Comprehensive test results for MingW-w64/MSYS2

[Arjen M. <Arj...@de...>]

Hi Alan,

> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@be...]
> Sent: Tuesday, July 14, 2015 11:23 AM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] Comprehensive test results for MingW-w64/MSYS2
>
> On 2015-07-14 06:55-0000 Arjen Markus wrote:
>
> > I send you the current results for the comprehensive test on
> MingW-w64/MSYS2, as I found some peculiar things. So this is the result I got
> yesterday, without the extra bits and pieces I intended to install.
>
> Hi Arjen:
>
> Congratulations on creating the first comprehensive test report for MinGW-
> w64/MSYS2!
>
> And I am pleased there were no errors.
>
Thanks, me too.

>
> > The peculiarities are:
>
> > - There is no wingcc device, because the gdi32 header file and
> library are missing. I just checked: they appear under /usr/include/w32api and
> /usr/lib/w32api.
>
> Could you clarify what you mean by that location?  It appears to me from looking at
> shared/output_tree/cmake.out that the MSYS2 stuff found by cmake is located in
> C:/msys64/usr.  Does that mean /usr/include/w32api and /usr/lib/w32api refer to a
> Cygwin location rather than a MSYS2 location?  Or is MSYS2 interpreting those as
> /C/msys64/usr/include/w32api and /C/msys64/usr/lib/w32api?
> I want to clarify that question, because I recall that MSYS reinterprets pathnames
> like that (and maybe Cygwin as well).
>

On my machine the actual directories (as reported by Windows) are c:\msys64\include\w32api and c:\msys64\lib\w32api, but the pwd command in the MSYS shell reports it as /usr/lib/w32api.

> Also, to ask the same question a different way, I noticed you had both /bin and
> /usr/bin on your PATH.  Should those be /C/msys64/bin and /C/msys64/usr/bin
> instead?  Or does MSYS2 interpret the former as the latter?
>
MSYS2 seems to do the same sort of trick Cygwin does. Directories /usr/bin and /bin appear to be one and the same - at least there is only one file "msys-2.0.dbg" according to Windows itself and MSYS2's find reports two of them.

> > - I wanted to know if there are many external dependencies (given
> the remark that MinGW-w64 is building on Cygwin), as that might cause problems
> distributing executable programs. "ldd" only reported the basic Windows DLLs but it
> did not report libplplot.dll.
>
> Is this the MSYS2 ldd command?

Yes, or perhaps the one that comes with the GCC package.


>
> > Very strange.
> Oh, and the native Windows tool I use for this type of inquiries reports both
> libplplot.dll AND msys-2.0.dll.
>
> > So there actually is a dependency on MSYS[2] stuff.
>
> In contrast, here is a result I got recently for the MinGW/MSYS case:
>
> bash.exe-3.1$ objdump -x \
> epa_build/Source/comprehensive_test_disposeable/shared/build_tree/dll/libplplot.dll
> \
> |fgrep -i "dll name:"
>          DLL Name: libcsirocsa.dll
>          DLL Name: libcsironn.dll
>          DLL Name: libqsastime.dll
>          DLL Name: libshp.dll
>          DLL Name: KERNEL32.dll
>          DLL Name: msvcrt.dll
>          DLL Name: msvcrt.dll
>
> i.e., no mention of msys-1.0.dll.  Does this objdump method give you a reliable result
> for the MinGW-w64/MSYS2 case (i.e, confirm your results obtained with the native
> Windows tool)? And if so do you confirm with both methods that there is no mention
> of the msys dll for the MinGW/MSYS case?

The output from ldd:
$ ldd x00c.exe
        ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x779d0000)
        kernel32.dll => /c/WINDOWS/system32/kernel32.dll (0x777b0000)
        KERNELBASE.dll => /c/WINDOWS/system32/KERNELBASE.dll (0x7fefd9c0000)

The output from objdump (filtered):
$ objdump -x x00c.exe |grep -i "dll name"
        DLL Name: libplplot.dll
        DLL Name: msys-2.0.dll
        DLL Name: KERNEL32.dll

>
> If that result (i.e., there is no dependency on the msys dll for the MinGW/MSYS
> platform, but there is a dependency on the msys2 dll for
> MinGW-w64-MSYS2 platform) is confirmed by you, then that result appears to be
> disappointing for the latter platform.  However, because we depend on other external
> dll's as well, I guess it doesn't matter so long as the msys2 dll is not that large.  So
> how does its size compare with the cygwin dll?

The sizes of the two are quite comparable - about 3.5 MB. Not all that much, though I have not checked what else is required.


>
> > Anyway, that is the quick report I can send at this moment.
>
> Thanks for that excellent first report for this platform. If you are pressed for time you
> can certainly just stop there until after the release. However, if you feel you have
> sufficient leisure time to broaden the test some time in the next few days by using
> the MSYS2 installer to install a lot more PLplot prerequisites, I would be happy to
> see those broadened test results as well.
>
> Note whenever you do such further MSYS2 installation please keep good notes of
> what packages you install so you can (eventually) use that information to provide
> content for a new page on our wiki documenting your recommendations for setting
> up PLplot builds on the MinGW-w64 platform.
>
Yes, I will do that.

Regards,

Arjen

DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.