public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Masamichi Hosoda <trueroad@trueroad.jp>
To: cygwin@cygwin.com, marco.atzeri@gmail.com
Cc: trueroad@trueroad.jp
Subject: Re: python-numpy (1.22.0-1) can't be imported
Date: Sat, 22 Jan 2022 10:04:35 +0900 (JST)	[thread overview]
Message-ID: <20220122.100435.1822912027393751150.trueroad@trueroad.jp> (raw)
In-Reply-To: <0fe2e36a-2f32-0334-0ff6-d164f56e1b48@gmail.com>

> 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

If I understand correctly,
the patch below is just a quick hack, but it solves the problem.

```
--- a/numpy/random/setup.py
+++ b/numpy/random/setup.py
@@ -147,7 +147,8 @@
                          include_dirs=['.', 'src', 'src/legacy'],
                          libraries=mtrand_libs,
                          extra_compile_args=EXTRA_COMPILE_ARGS,
-                         extra_link_args=EXTRA_LINK_ARGS,
+                         extra_link_args=(EXTRA_LINK_ARGS +
+                                          ['-Wl,--export-all-symbols']),
                          depends=depends + ['mtrand.pyx'],
                          define_macros=defs + LEGACY_DEFS,
                          )
```

  reply	other threads:[~2022-01-22  1:04 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
2022-01-22  1:04       ` Masamichi Hosoda [this message]
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=20220122.100435.1822912027393751150.trueroad@trueroad.jp \
    --to=trueroad@trueroad.jp \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).