From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: mingw cross tests missing DLLs - CROSS_BINDIR not in PATH
Date: Mon, 4 Mar 2024 14:20:48 -0700 [thread overview]
Message-ID: <f807e9c0-a411-4e32-8eaf-985337411f20@SystematicSw.ab.ca> (raw)
In-Reply-To: <91a1b888-07ad-40e4-acaf-793521302d44@dronecode.org.uk>
On 2024-03-04 13:00, Jon Turney wrote:
> On 03/03/2024 22:29, Brian Inglis via Cygwin-apps wrote:
>> On 2024-03-03 14:39, Jon Turney via Cygwin-apps wrote:
>>> On 03/03/2024 16:48, Brian Inglis via Cygwin-apps wrote:
>>>> I am finding mingw package cross tests fail with missing DLLs - CROSS_BINDIR
>>>> is not in the PATH.
>>>>
>>>> I now have to define src_test to run cygtest adding CROSS_BINDIR in the PATH.
>>>>
>>>> Is this likely to be upstream (e.g. gnulib) changes or cygport changes?
>>
>>> This is a shortcoming of cygport, in that you cannot just write "do the
>>> standard src_(compile|install|test), but do this extra thing first (like
>>> modifying PATH as you need in this case).
>>>
>>> (One approach to this I've though about would be to have a hook function (or
>>> set of functions) which are called before each phase of operation, to allow
>>> this)
>>
>> These test failures have been only in the latest upstream releases.
>> Previously no PATH fiddling was required.
>> For mingw64-x86_64-nghttp2 that was 2024-01-21.
>>
>> Why I asked if anyone noticed any cross build changes as for example in
>> autotools, gnulib, or cygport?
>
> I assumed that you were talking about "PATH needs to be set so that dependencies
> of the built DLL can be loaded"
>
> But, now I look, mingw64-x86_64-nghttp2 doesn't have any dependencies.
>
> So, I'm not so sure. Maybe you just mean that the test harness can't locate the
> just built DLL? That could well be an upstream change.
>
> Maybe you could show the actual error?
Sorry I was not clearer.
In previous release build checks there were no issues.
In the latest release the test programs have a dependency on winpthreads and
failed with popup dialogues:
main.exe - System Error ...
ALSO
failmalloc.exe - System Error
X
The code execution cannot proceed because
libwinpthread-1.dll was not found.
Reinstalling the program may fix this problem.
$ cygcheck -f /usr/x86_64-w64-mingw32/sys-root/mingw/bin/libwinpthread-1.dll
mingw64-x86_64-winpthreads-11.0.1-1
Similar result as:
$ cygcheck mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/{main,failmalloc}
cygcheck: track_down: could not find libwinpthread-1.dll
C:/.../usr/src/nghttp2/mingw64-x86_64-nghttp2/mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/main.exe
C:/WINDOWS/system32/KERNEL32.dll
C:/WINDOWS/system32/ntdll.dll
C:/WINDOWS/system32/KERNELBASE.dll
C:/WINDOWS/system32/msvcrt.dll
cygcheck: track_down: could not find libwinpthread-1.dll
C:/.../usr/src/nghttp2/mingw64-x86_64-nghttp2/mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/failmalloc.exe
C:/WINDOWS/system32/KERNEL32.dll
C:/WINDOWS/system32/ntdll.dll
C:/WINDOWS/system32/KERNELBASE.dll
C:/WINDOWS/system32/msvcrt.dll
$ PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/bin/:$PATH" \
cygcheck mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/{main,failmalloc}
C:/.../usr/src/nghttp2/mingw64-x86_64-nghttp2/mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/main.exe
C:/WINDOWS/system32/KERNEL32.dll
C:/WINDOWS/system32/ntdll.dll
C:/WINDOWS/system32/KERNELBASE.dll
C:/WINDOWS/system32/msvcrt.dll
C:/.../usr/x86_64-w64-mingw32/sys-root/mingw/bin/libwinpthread-1.dll
C:/.../usr/src/nghttp2/mingw64-x86_64-nghttp2/mingw64-x86_64-nghttp2-1.60.0-1.noarch/build/tests/failmalloc.exe
C:/WINDOWS/system32/KERNEL32.dll
C:/WINDOWS/system32/ntdll.dll
C:/WINDOWS/system32/KERNELBASE.dll
C:/WINDOWS/system32/msvcrt.dll
C:/.../usr/x86_64-w64-mingw32/sys-root/mingw/bin/libwinpthread-1.dll
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-03-04 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 16:48 Brian Inglis
2024-03-03 21:39 ` Jon Turney
2024-03-03 22:29 ` Brian Inglis
2024-03-04 20:00 ` Jon Turney
2024-03-04 21:20 ` Brian Inglis [this message]
2024-03-05 15:32 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f807e9c0-a411-4e32-8eaf-985337411f20@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).