From: brendan detracey <brendandetracey@yahoo.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: eccodes
Date: Sun, 11 Apr 2021 21:53:21 +0000 (UTC) [thread overview]
Message-ID: <719120829.476733.1618178001957@mail.yahoo.com> (raw)
In-Reply-To: <ff78b501-79ad-2d66-1965-3e14af1018ef@gmail.com>
That worked Marco. Thanks guys!How did "cygmake test" know it had to call "ctest"? In the eccodes instructions, "ctest" is the command.
Why doesn't cygport automatically symlink the cyg*dll files for tests?
-------------------------brendandetracey@yahoo.com
On Sunday, April 11, 2021, 04:43:41 p.m. ADT, Marco Atzeri via Cygwin-apps <cygwin-apps@cygwin.com> wrote:
On 11.04.2021 20:53, Brian Inglis wrote:
> On 2021-04-11 12:01, Achim Gratz wrote:
>> brendan detracey via Cygwin-apps writes:
>>> eccodes builds out of the box, more or less. However, all tests fail
>>> because the cyg*.dll's weren't copied to ${B}/bin. (They were handled
>>> properly when built without cygport i.e. copied from src and fortran
>>> subdirs of the build dir.)
>>
>> Hard to say without a log why that happens, but you should start with
>> checking whether the copy is even attempted.
>
> DLLs should be built in $B/.../, installed in $D/bin/, and the tests
> have to run with $D/bin/ in their path.
> Not sure if this is automatic, you may have to override src_test, or
> patch the test setup to add that.
>
Brendan,
no idea why on your build the installation is under /usr/local
for me everything is in the right place.
Please verify if you have some settings interfering
Attached version that allows tests to be passed
Regards
Marco
next prev parent reply other threads:[~2021-04-11 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1777022414.443732.1618159734064.ref@mail.yahoo.com>
2021-04-11 16:48 ` eccodes brendan detracey
2021-04-11 18:01 ` eccodes Achim Gratz
2021-04-11 18:53 ` eccodes Brian Inglis
2021-04-11 19:43 ` eccodes Marco Atzeri
2021-04-11 21:53 ` brendan detracey [this message]
2021-04-12 7:07 ` eccodes Marco Atzeri
2021-04-12 19:22 ` eccodes Achim Gratz
2021-04-12 22:46 ` eccodes Brian Inglis
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=719120829.476733.1618178001957@mail.yahoo.com \
--to=brendandetracey@yahoo.com \
--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).