public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: cygwin-apps@cygwin.com
Subject: Re: mingw cross tests missing DLLs - CROSS_BINDIR not in PATH
Date: Mon, 4 Mar 2024 20:00:31 +0000	[thread overview]
Message-ID: <91a1b888-07ad-40e4-acaf-793521302d44@dronecode.org.uk> (raw)
In-Reply-To: <5aab37d9-db10-4af2-b6e0-b5ff74d1180d@SystematicSw.ab.ca>

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?


  reply	other threads:[~2024-03-04 20:00 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 [this message]
2024-03-04 21:20       ` Brian Inglis
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=91a1b888-07ad-40e4-acaf-793521302d44@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=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).