* liblapack-devel seems to be missing liblapack0 dependency
[not found] <c2e1cdaa-a2a3-41a6-a896-b847f3c4ab75.ref@aol.com>
@ 2023-11-30 20:23 ` airplanemath
2023-11-30 21:05 ` Jon Turney
0 siblings, 1 reply; 3+ messages in thread
From: airplanemath @ 2023-11-30 20:23 UTC (permalink / raw)
To: cygwin
To whom it may concern,
An automated script started failing yesterday, apparently because it
could not
find the lapack and blas DLLs. On investigation, only liblapack-devel
was installed,
not liblapack0. Should we be updating scripts to explicitly install
liblapack0 when
using some executable linked with liblapack-devel?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: liblapack-devel seems to be missing liblapack0 dependency
2023-11-30 20:23 ` liblapack-devel seems to be missing liblapack0 dependency airplanemath
@ 2023-11-30 21:05 ` Jon Turney
2023-11-30 21:11 ` Marco Atzeri
0 siblings, 1 reply; 3+ messages in thread
From: Jon Turney @ 2023-11-30 21:05 UTC (permalink / raw)
To: airplanemath, Marco Atzeri, The Cygwin Mailing List
On 30/11/2023 20:23, airplanemath via Cygwin wrote:
> To whom it may concern,
>
> An automated script started failing yesterday, apparently because it
> could not
> find the lapack and blas DLLs. On investigation, only liblapack-devel
> was installed,
> not liblapack0. Should we be updating scripts to explicitly install
> liblapack0 when
> using some executable linked with liblapack-devel?
>
No. I think this was a build error in a recent lapack update.
Marco,
I adjusted this on sourceware.
I think the cygport maybe needs something like
DEPS_PATH="/usr/lib/lapack/" for the dependency to be automatically
detected correctly, if libpack0 isn't already installed.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: liblapack-devel seems to be missing liblapack0 dependency
2023-11-30 21:05 ` Jon Turney
@ 2023-11-30 21:11 ` Marco Atzeri
0 siblings, 0 replies; 3+ messages in thread
From: Marco Atzeri @ 2023-11-30 21:11 UTC (permalink / raw)
To: Jon Turney, airplanemath, The Cygwin Mailing List
On 30/11/2023 22:05, Jon Turney wrote:
> On 30/11/2023 20:23, airplanemath via Cygwin wrote:
>> To whom it may concern,
>>
>> An automated script started failing yesterday, apparently because it
>> could not
>> find the lapack and blas DLLs. On investigation, only liblapack-devel
>> was installed,
>> not liblapack0. Should we be updating scripts to explicitly install
>> liblapack0 when
>> using some executable linked with liblapack-devel?
>>
>
> No. I think this was a build error in a recent lapack update.
>
> Marco,
>
> I adjusted this on sourceware.
>
> I think the cygport maybe needs something like
> DEPS_PATH="/usr/lib/lapack/" for the dependency to be automatically
> detected correctly, if libpack0 isn't already installed.
>
correct.
I will look for most effective solutions
Thanks
Marco
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-11-30 21:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <c2e1cdaa-a2a3-41a6-a896-b847f3c4ab75.ref@aol.com>
2023-11-30 20:23 ` liblapack-devel seems to be missing liblapack0 dependency airplanemath
2023-11-30 21:05 ` Jon Turney
2023-11-30 21:11 ` Marco Atzeri
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).