From: Marco Atzeri <marco.atzeri@gmail.com>
To: Masamichi Hosoda <trueroad@trueroad.jp>, cygwin@cygwin.com
Subject: Re: python-numpy (1.22.0-1) can't be imported
Date: Sat, 22 Jan 2022 06:24:48 +0100 [thread overview]
Message-ID: <89f4e748-9e1c-b0de-834b-2511b988f14a@gmail.com> (raw)
In-Reply-To: <20220122.100435.1822912027393751150.trueroad@trueroad.jp>
On 22.01.2022 02:04, Masamichi Hosoda wrote:
>> 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,
> )
> ```
Thanks
It is something like that, but "-Wl,--export-all-symbols"
is not used on 1.21.4 and is not needed for most of the other
modules on 1.22.x
so I am looking for a less extreme action.
Also to understand how it can impact other python subpackages
Regards
Marco
next prev parent reply other threads:[~2022-01-22 5:24 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
2022-01-22 5:24 ` Marco Atzeri [this message]
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=89f4e748-9e1c-b0de-834b-2511b988f14a@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=trueroad@trueroad.jp \
/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).