ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1451
Location: Berlin, Germany
|
 Posted: Wed May 29, 2024 1:20 pm Post subject: media-libs/aubio-0.4.9-r2 emerge segfaults on Numpy modules |
 |
|
To wit:
| Code: | >>> Compiling source in /var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9 ...
"/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waf" build --verbose --jobs=17 --notests
Waf: Entering directory `/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/build'
A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0rc2 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.
Traceback (most recent call last): File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waf", line 165, in <module>
Scripting.waf_entry_point(cwd, VERSION, wafdir)
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Scripting.py", line 119, in waf_entry_point
run_commands()
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Scripting.py", line 179, in run_commands
ctx=run_command(cmd_name)
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Scripting.py", line 170, in run_command
ctx.execute()
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Scripting.py", line 367, in execute
return execute_method(self)
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Build.py", line 93, in execute
self.execute_build()
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Build.py", line 96, in execute_build
self.recurse([self.run_dir])
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/waflib/Context.py", line 126, in recurse
user_function(self)
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/wscript", line 517, in build
sphinx(bld)
File "/var/tmp/portage/media-libs/aubio-0.4.9-r2/work/aubio-0.4.9/wscript", line 566, in sphinx
import aubio
File "/usr/lib/python3.11/site-packages/aubio/__init__.py", line 26, in <module>
from ._aubio import __version__ as version
Unable to import Numpy array from aubio module (error -1)
Unable to import Numpy umath from aubio module (error -1)
/var/tmp/portage/media-libs/aubio-0.4.9-r2/temp/environment: line 5004: 32 Segmentation fault "${WAF_BINARY}" ${_mywafconfig} ${jobs} "${@}"
|
How do I find out which modules need to be rebuilt? Or rather, which modules specifically are causing the segfault? Is it the last two, "array" and "umath"? How do I find out which package owns those and rebuild it with numpy-2 support, as the initial warning recommends? Is this related to this bug, that aubio lacks python-3.12 support?
Cheers,
EE |
|
Portage & Programming
