[MacPorts] #63072: py39-numpy @1.20.3_0+gcc11+openblas fails to build on aarch64

MacPorts noreply at macports.org
Fri Dec 10 07:43:58 UTC 2021


#63072: py39-numpy @1.20.3_0+gcc11+openblas fails to build on aarch64
-----------------------------+-----------------------
  Reporter:  thermalecology  |      Owner:  michaelld
      Type:  defect          |     Status:  closed
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.7.1
Resolution:  fixed           |   Keywords:  arm64
      Port:  py-numpy        |
-----------------------------+-----------------------

Comment (by Guymer):

 Whilst I have been able to get `gcc11` to build (by using the patch in
 [ticket:63677]) I have not been able to install `py39-numpy` as I have
 been getting the same error. I uninstalled `gcc11` (and all `+gcc11`
 ports), I installed `gcc-devel` instead and I still get the same error
 (after running `port clean py39-numpy`).

 For info:

 {{{
 sh-3.2# port installed | grep gcc
   fftw-3 @3.3.10_0+gccdevel (active)
   gcc-devel @12-20211127_0 (active)
   gcc_select @0.1_9 (active)
   libgcc-devel @12-20211127_0 (active)
   OpenBLAS @0.3.18_0+gccdevel+lapack+native (active)
 }}}

 For info:

 {{{
 sh-3.2# port select --summary | grep gcc
 gcc         mp-gcc-devel   mp-gcc-devel none
 }}}

 The failed build:

 {{{
 sh-3.2# grep error
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
 .org_macports_release_tarballs_ports_python_py-numpy/py39-numpy/main.log
 ...
 :info:build /opt/local/lib/gcc-devel/gcc/aarch64-apple-darwin21/12.0.0
 /include-fixed/math.h:68:5: error: #error "Unsupported value of
 __FLT_EVAL_METHOD__."
 :info:build    68 | #   error "Unsupported value of __FLT_EVAL_METHOD__."
 ...
 }}}

 I find it interesting that when I list the `lib` folder it appears as if
 the `libgcc` files have not been updated.

 {{{
 sh-3.2# ls -hl /opt/local/lib/libgcc/
 total 2152
 -rwxr-xr-x  1 root  admin    70K 30 Nov 19:37 libatomic.1.dylib
 -rwxr-xr-x  1 root  admin    85K 30 Nov 19:37 libgcc_s.1.1.dylib
 -rwxr-xr-x  1 root  admin   1.0M 30 Nov 19:37 libgfortran.5.dylib
 -rwxr-xr-x  1 root  admin   257K 30 Nov 19:37 libgomp.1.dylib
 -rwxr-xr-x  1 root  admin   124K 30 Nov 19:37 libitm.1.dylib
 -rwxr-xr-x  1 root  admin   113K 30 Nov 19:37 libobjc-gnu.4.dylib
 -rwxr-xr-x  1 root  admin    34K 30 Nov 19:37 libssp.0.dylib
 -rwxr-xr-x  1 root  admin   2.0M 30 Nov 19:37 libstdc++.6.dylib
 }}}

 Is it possible that `gcc11` did not clean up after itself when it was
 uninstalled? Given that I was able to get `gcc11` to install at the start,
 why didn't `py39-numpy` then install? Surely I should not need to revert
 to `gcc-devel` if I can get `gcc11` to install.

-- 
Ticket URL: <https://trac.macports.org/ticket/63072#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list