Opened 4 years ago
Last modified 4 years ago
#60637 assigned defect
scalapack 2.1.0 +gcc10: ld: file not found: /usr/lib/system/libsystem_darwin.dylib
Reported by: | dstrubbe (David Strubbe) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) | |
Port: | scalapack |
Description
Configure fails for gcc10 but works fine for gcc9. Sierra 10.12.6, XCode 9.2.
-- Compiling and Building BLACS INSTALL Testing to set correct variables -- Configure in the INSTALL directory successful -- Build Output: Scanning dependencies of target xintface [ 33%] Building Fortran object CMakeFiles/xintface.dir/Fintface.f.o [ 66%] Building C object CMakeFiles/xintface.dir/Cintface.c.o [100%] Linking Fortran executable xintface -- Error Output: ld: file not found: /usr/lib/system/libsystem_darwin.dylib for architecture x86_64 collect2: error: ld returned 1 exit status gmake[2]: *** [CMakeFiles/xintface.dir/build.make:119: xintface] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:96: CMakeFiles/xintface.dir/all] Error 2 gmake: *** [Makefile:104: all] Error 2 CMake Error at CMAKE/FortranMangling.cmake:42 (MESSAGE): Build in the BLACS INSTALL directory FAILED Call Stack (most recent call first): CMakeLists.txt:122 (COMPILE) -- Configuring incomplete, errors occurred! See also "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_scalapack/scalapack/work/build/CMakeFiles/CMakeOutput.log". Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_scalapack/scalapack/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=ON -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.12" -DCMAKE_OSX_SYSROOT="/" -DMPI_C_COMPILER=mpicc-mpich-mp -DMPI_Fortran_COMPILER=mpif90-mpich-mp -DMPIEXEC=/opt/local/bin/mpiexec-mpich-mp -DLAPACK_LIBRARIES="-L/opt/local/lib -lvecLibFort" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_scalapack/scalapack/work/scalapack-2.1.0 Exit code: 1 Error: Failed to configure scalapack: configure failure: command execution failed
Change History (4)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | scalapack 2.1.0 +gcc10: configure fails → scalapack 2.1.0 +gcc10: ld: file not found: /usr/lib/system/libsystem_darwin.dylib |
---|
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
To be more precise:
On 10.11 with Xcode 8.2.1 we saw:
ld: file not found: /usr/lib/system/libsystem_symptoms.dylib for architecture x86_64
Both Xcode 8.2.1 and the corresponding command lines tools contain only the 10.12 SDK. The 10.12 SDK contains /usr/lib/system/libsystem_symptoms.tbd but OS X 10.11 itself does not contain /usr/lib/system/libsystem_symptoms.dylib.
On 10.12 with Xcode 9.2 you saw:
ld: file not found: /usr/lib/system/libsystem_darwin.dylib for architecture x86_64
Both Xcode 9.2 and the corresponding command line tools contain only the 10.13 SDK. The 10.13 SDK contains /usr/lib/system/libsystem_darwin.tbd but macOS 10.12 itself does not contain /usr/lib/system/libsystem_darwin.dylib.
This makes me wonder if something—gfortran?—is looking at the SDK to determine what capabilities it should use, not taking into account that not all of the capabilities advertised by the SDK are actually available on the running OS.
comment:3 Changed 4 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:4 Changed 4 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy removed |
---|
Yes, this problem occurs on our buildbot too.