public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: python-numpy (1.22.0-1) can't be imported
Date: Tue, 18 Jan 2022 21:55:54 +0100	[thread overview]
Message-ID: <0fe2e36a-2f32-0334-0ff6-d164f56e1b48@gmail.com> (raw)
In-Reply-To: <vriu8rvj13ah.fsf@mail.aol.com>

On 14.01.2022 03:04, airplanemath via Cygwin wrote:
> On Wed, Jan 12 2022, Marco Atzeri wrote:
> 
>> On 12.01.2022 12:47, ggl329 wrote:
>>> Hi Marco,
>>> I upgraded python39-numpy to 1.22.0-1, and failed to import numpy.
>>> It seems that mtrand.cpython-39-x86_64-cygwin.dll does not have
>>> PyInit_mtrand.
>>> Could you check if numpy can be imported in your environment?
>>>
>>
>> working on it.
>> In theory I have not changed the build between the two versions
>> but there was a patch in 1.19.4-1 for similar issue.
>>
>> Regards
>> Marco
> 
> I have the same problems with the distribution NumPy package, but I can
> use a locally-compiled NumPy with no patches.  It doesn't look like your
> build has any patches either:
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpython-numpy-src%2Fpython-numpy-1.22.0-1-src&grep=numpy
> so that's fun.
> 
> Out of curiousity, what options are you passing for cpu-baseline and
> cpu-dispatch?
> https://numpy.org/devdocs/reference/simd/build-options.html
> I don't see the newest cygport in the Cygwin package repository.

I have not found the root cause yet.
As the  1.21.4-1 imports correctly I removed the 1.22.0-1 until I solve 
the issue.

I do not see anything obvious in upstream source between 1.21.4 and 
1.22.0 that gives me any hint on root cause.

Also 1.22.1 shows the same problem.
I excluded the build chain as rebuilding 1.19.4 worked fine
for all 3.6 to 3.9

Regards
Marco








  reply	other threads:[~2022-01-18 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 11:47 ggl329
2022-01-12 22:16 ` Marco Atzeri
2022-01-14  2:04   ` airplanemath
2022-01-18 20:55     ` Marco Atzeri [this message]
2022-01-22  1:04       ` Masamichi Hosoda
2022-01-22  5:24         ` Marco Atzeri
2022-01-22 10:16           ` Masamichi Hosoda
2022-01-23  9:42             ` Masamichi Hosoda
2022-02-06 17:35             ` airplanemath

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=0fe2e36a-2f32-0334-0ff6-d164f56e1b48@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).