pyton 3.11 build log

build-python3_11.log (text/x-log), 15.33 KB, created by Anton Gubarkov on 2023-09-18 08:43:44 UTC

 [32m*[0m python3_11: running distutils-r1_run_phase python_configure_all
 [32m*[0m python3_11: running distutils-r1_run_phase distutils-r1_python_compile
 [32m*[0m   Building the wheel for numpy-1.26.0 via mesonpy
gpep517 build-wheel --backend mesonpy --output-fd 3 --wheel-dir /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11/wheel --config-json {"builddir": "/var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11", "setup-args": ["-Dblas=", "-Dlapack="], "compile-args": ["-v", "-j6", "-l0"]}
2023-09-17 22:46:15,195 gpep517 INFO Building wheel via backend mesonpy
+ /usr/bin/python3.11 /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0/vendored-meson/meson/meson.py setup /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0 /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11 -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md -Dblas= -Dlapack= --native-file=/var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11/meson-python-native-file.ini
The Meson build system
Version: 1.2.99
Source dir: /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0
Build dir: /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11
Build type: native build
Project name: NumPy
Project version: 1.26.0
C compiler for the host machine: gcc (gcc 13.2.1 "gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826")
C linker for the host machine: gcc ld.bfd 2.41
C++ compiler for the host machine: g++ (gcc 13.2.1 "g++ (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826")
C++ linker for the host machine: g++ ld.bfd 2.41
Cython compiler for the host machine: cython (cython 3.0.2)
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python found: YES (/usr/bin/python3.11)
Found pkg-config: /usr/bin/pkg-config (2.0.3)
Run-time dependency python found: YES 3.11
Has header "Python.h" with dependency python-3.11: YES 
Compiler for C supports arguments -fno-strict-aliasing: YES 
Message: Appending option "detect" to "cpu-baseline" due to detecting global architecture c_arg "-march=native"
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,-O1 looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
WARNING: -Wl,--as-needed looks like a linker argument, but has_argument and other similar methods only support checking compiler arguments. Using them to check linker arguments are never supported, and results are likely to be wrong regardless of the compiler you are using. has_link_argument or other similar method can be used instead.
Test features "SSE SSE2 SSE3 SSSE3 SSE41 POPCNT SSE42 AVX XOP FMA4 F16C FMA3 AVX2 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL AVX512_SPR" : Parial support, missing(XOP FMA4 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL AVX512_SPR) 
Test features "SSE SSE2 SSE3 SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2" : Supported 
Test features "AVX512F" : Supported 
Test features "AVX512CD" : Supported 
Test features "AVX512_KNL" : Supported 
Test features "AVX512_KNM" : Supported 
Test features "AVX512_SKX" : Supported 
Test features "AVX512_CLX" : Supported 
Test features "AVX512_CNL" : Supported 
Test features "AVX512_ICL" : Supported 
Test features "AVX512_SPR" : Supported 
Configuring npy_cpu_dispatch_config.h using configuration
Message: 
CPU Optimization Options
  baseline:
    Requested : min+detect
    Enabled   : SSE SSE2 SSE3 SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2
  dispatch:
    Requested : max -xop -fma4
    Enabled   : AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL AVX512_SPR

Library m found: YES

../numpy-1.26.0/numpy/meson.build:207:4: ERROR: Problem encountered: No BLAS library detected! Install one, or use the `allow-noblas` build option (note, this may be up to 100x slower for some linear algebra operations).

A full log can be found at /var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11/meson-logs/meson-log.txt
 [31;01m*[0m ERROR: dev-python/numpy-1.26.0::gentoo failed (compile phase):
 [31;01m*[0m   Wheel build failed
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m     ebuild.sh, line  136:  Called src_compile
 [31;01m*[0m   environment, line 5070:  Called distutils-r1_src_compile
 [31;01m*[0m   environment, line 2971:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 1652:  Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 4659:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 4147:  Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 4145:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 2255:  Called distutils-r1_run_phase 'distutils-r1_python_compile'
 [31;01m*[0m   environment, line 2953:  Called distutils-r1_python_compile
 [31;01m*[0m   environment, line 2772:  Called distutils_pep517_install '/var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0-python3_11/install'
 [31;01m*[0m   environment, line 3304:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m       local wheel=$("${cmd[@]}" 3>&1 1>&2 || die "Wheel build failed");
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the output of `emerge --info '=dev-python/numpy-1.26.0::gentoo'`,
 [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-python/numpy-1.26.0::gentoo'`.
 [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-python/numpy-1.26.0/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-python/numpy-1.26.0/temp/environment'.
 [31;01m*[0m Working directory: '/var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0'
 [31;01m*[0m S: '/var/tmp/portage/dev-python/numpy-1.26.0/work/numpy-1.26.0'