public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Numpy 1.12.1 setup issue (targetting Python 3.6.1) from Cygwin 2.8.0
Date: Wed, 26 Apr 2017 08:19:00 -0000	[thread overview]
Message-ID: <da568fec-fd55-fb54-6fc5-8b107d296dd4@SystematicSw.ab.ca> (raw)
In-Reply-To: <a9f42517-3f09-faf6-80e4-d331e9725441@cs.umass.edu>

On 2017-04-25 11:17, Eliot Moss wrote:
> On 4/25/2017 12:34 PM, Erik Bray wrote:
>> I've just started having this problem too. There appears to be a 
>> bug in the latest version of the liblapack0 package, because the 
>> import lib liblapack.dll.a lists the lapack DLL name as 
>> "cyglapack.dll", when it should be "cyglapack-0.dll".
>> Copying /lib/lapack/cyglapack-0.dll to /lib/lapack/cyglapack.dll
>> works as a workaround...
> I suspect that adding a symlink from cyglapack.dll to
> cyglapack-0.dll would also work, if one prefers that solution.

ISTR a discussion around rebase recently where symlinks do not 
work because Windows kernel loads the DLLs.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-04-25 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 12:44 Kptain
2017-04-16 18:22 ` Marco Atzeri
2017-04-16 18:24 ` Kptain
2017-04-16 19:03   ` Eliot Moss
2017-04-17 17:59     ` Kptain
2017-04-25 18:07       ` Erik Bray
2017-04-26  1:51         ` Eliot Moss
2017-04-26  8:19           ` Brian Inglis [this message]
2017-04-26  9:20             ` Eliot Moss
2017-04-26 15:21             ` Kptain

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=da568fec-fd55-fb54-6fc5-8b107d296dd4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@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).