Opened 6 years ago
Closed 6 years ago
#58063 closed defect (fixed)
py37-numpy @1.15.4_0+gfortran+openblas: cannot upgrade to @1.16.1_0 on High Sierra
Reported by: | hugo-ribeiro (Hugo Ribeiro) | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | Cc: | mf2k (Frank Schima), michaellass (Michael Lass), wwilly (Willy Wolff), captainproton1971 (Captain Proton), stromnov (Andrey Stromnov), jjstickel (Jonathan Stickel) | |
Port: | py-numpy |
Description
It seems that there is an invalid option that is being passed to the linker.
/usr/bin/clang -bundle -undefined dynamic_lookup -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 build/temp.macosx-10.13-x86_64-3.7/numpy/linalg/lapack_litemodule.o build/temp.macosx-10.13-x86_64-3.7/numpy/linalg/lapack_lite/python_xerbla.o -L/opt/local/lib -Lbuild/temp.macosx-10.13-x86_64-3.7 -L/opt/local/lib -lopenblas -lopenblas -o build/lib.macosx-10.13-x86_64-3.7/numpy/linalg/lapack_lite.cpython-37m-darwin.so -undefined dynamic_lookup -bundle ld: invalid option to -undefined [ warning | error | suppress | dynamic_lookup ] clang: error: linker command failed with exit code 1 (use -v to see invocation)
I've also attached "main.log"
Attachments (3)
Change History (15)
Changed 6 years ago by hugo-ribeiro (Hugo Ribeiro)
comment:1 Changed 6 years ago by mf2k (Frank Schima)
Cc: | michaelld removed |
---|---|
Owner: | set to michaelld |
Port: | py-numpy added; py37-numpy removed |
Status: | new → assigned |
comment:2 Changed 6 years ago by mf2k (Frank Schima)
comment:3 Changed 6 years ago by mf2k (Frank Schima)
Cc: | mf2k added |
---|
comment:4 Changed 6 years ago by lpsinger (Leo Singer)
I'm seeing the same error on macOS Mojave 10.14.3. Attaching my build log.
comment:5 Changed 6 years ago by michaellass (Michael Lass)
Cc: | michaellass added |
---|
comment:6 Changed 6 years ago by wwilly (Willy Wolff)
Cc: | wwilly added |
---|
comment:7 Changed 6 years ago by captainproton1971 (Captain Proton)
Cc: | captainproton1971 added |
---|
Getting the same building py27-numpy +gfortran +openblas on Mojave 10.14.3 (18D109).
sudo port install py27-numpy +gfortran +openblas ---> Computing dependencies for py27-numpy ---> Fetching archive for py27-numpy ---> Attempting to fetch py27-numpy-1.16.1_0+gfortran+openblas.darwin_18.x86_64.tbz2 from https://packages.macports.org/py27-numpy ---> Attempting to fetch py27-numpy-1.16.1_0+gfortran+openblas.darwin_18.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/py27-numpy ---> Attempting to fetch py27-numpy-1.16.1_0+gfortran+openblas.darwin_18.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/py27-numpy ---> Fetching distfiles for py27-numpy ---> Verifying checksums for py27-numpy ---> Extracting py27-numpy ---> Applying patches to py27-numpy ---> Configuring py27-numpy ---> Building py27-numpy Error: Failed to build py27-numpy: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-numpy/py27-numpy/main.log for details.
Same error seems to be being recorded in main.log (I've attached mine too, if there's a subtle difference I've missed).
Changed 6 years ago by captainproton1971 (Captain Proton)
Attachment: | main.3.log added |
---|
py27-numpy on Mojave 10.14.3 (18D109)
comment:8 Changed 6 years ago by michaellass (Michael Lass)
A workaround for people needing to rebuild py-numpy now: Using +gcc8 instead of +gfortran fixes the problem for me. I tested py27-numpy and py37-numpy with +gcc8 +openblas on Mojave.
comment:9 Changed 6 years ago by stromnov (Andrey Stromnov)
Cc: | stromnov added |
---|
comment:10 Changed 6 years ago by jjstickel (Jonathan Stickel)
Cc: | jjstickel added |
---|
comment:11 Changed 6 years ago by jjstickel (Jonathan Stickel)
Same problem on Sierra (10.12.6) with py36-numpy +gfortran +openblas, so it seems like it is not OS-specific but is rather the variants.
comment:12 Changed 6 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Guessing this issue is actually a duplicate of #58114, and thus was closed by https://trac.macports.org/changeset/c5dea4548c794745e202b0ba611240fbd55b3b9a/macports-ports .
I see the same error.