[MacPorts] #42875: Geant4: fails to link against CLHEP with clang 3.4
MacPorts
noreply at macports.org
Wed Apr 9 11:12:45 PDT 2014
#42875: Geant4: fails to link against CLHEP with clang 3.4
--------------------------------+--------------------------------
Reporter: graziosi.angelo@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords:
Port: geant4 |
--------------------------------+--------------------------------
Comment (by jonesc@…):
Hi,
Build géant 4.10.0 on OSX 10.9, with the blacklist as currently in the
port
{{{
compiler.blacklist {clang > 503} macports-clang-3.4 macports-clang-3.5
}}}
The build ends up resorting to the compiler /opt/local/bin/llvm-g++-4.2,
which immediately struck me as probably not a great choice, and ultimately
fails with
{{{
/opt/local/bin/llvm-g++-4.2 -pipe -Os -I/opt/local/include -arch x86_64
-W -Wall -pedantic -Wno-non-virtual-dtor -Wno-long-long -Wwrite-strings
-Wpointer-arith -Woverloaded-virtual -Wno-variadic-macros -Wshadow -pipe
-std=c++98 -DNDEBUG -arch x86_64 -dynamiclib
-Wl,-headerpad_max_install_names -L/opt/local/lib
-Wl,-headerpad_max_install_names -arch x86_64 -o
../../outputs/library/Darwin-g++/libG4analysis.dylib -install_name
/opt/local/lib/Geant4/Geant4.10.0/libG4analysis.dylib
CMakeFiles/G4analysis.dir/csv/src/G4CsvAnalysisManager.cc.o
CMakeFiles/G4analysis.dir/csv/src/G4CsvFileManager.cc.o
CMakeFiles/G4analysis.dir/csv/src/G4CsvNtupleManager.cc.o
CMakeFiles/G4analysis.dir/hntools/src/G4H1DummyManager.cc.o
CMakeFiles/G4analysis.dir/hntools/src/G4H1ToolsManager.cc.o
CMakeFiles/G4analysis.dir/hntools/src/G4H2DummyManager.cc.o
CMakeFiles/G4analysis.dir/hntools/src/G4H2ToolsManager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4AnalysisVerbose.cc.o
CMakeFiles/G4analysis.dir/management/src/G4AnalysisManagerState.cc.o
CMakeFiles/G4analysis.dir/management/src/G4AnalysisMessenger.cc.o
CMakeFiles/G4analysis.dir/management/src/G4BaseAnalysisManager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4AnalysisUtilities.cc.o
CMakeFiles/G4analysis.dir/management/src/G4BinScheme.cc.o
CMakeFiles/G4analysis.dir/management/src/G4Fcn.cc.o
CMakeFiles/G4analysis.dir/management/src/G4FileMessenger.cc.o
CMakeFiles/G4analysis.dir/management/src/G4H1Messenger.cc.o
CMakeFiles/G4analysis.dir/management/src/G4H2Messenger.cc.o
CMakeFiles/G4analysis.dir/management/src/G4HnManager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4HnMessenger.cc.o
CMakeFiles/G4analysis.dir/management/src/G4VAnalysisManager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4VFileManager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4VH1Manager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4VH2Manager.cc.o
CMakeFiles/G4analysis.dir/management/src/G4VNtupleManager.cc.o
CMakeFiles/G4analysis.dir/root/src/G4RootAnalysisManager.cc.o
CMakeFiles/G4analysis.dir/root/src/G4RootFileManager.cc.o
CMakeFiles/G4analysis.dir/root/src/G4RootNtupleManager.cc.o
CMakeFiles/G4analysis.dir/xml/src/G4XmlAnalysisManager.cc.o
CMakeFiles/G4analysis.dir/xml/src/G4XmlFileManager.cc.o
CMakeFiles/G4analysis.dir/xml/src/G4XmlNtupleManager.cc.o
../../outputs/library/Darwin-g++/libG4global.dylib
../../outputs/library/Darwin-g++/libG4intercoms.dylib
../../outputs/library/Darwin-g++/libG4zlib.dylib
../../outputs/library/Darwin-g++/libG4global.dylib
/opt/local/lib/libCLHEP.dylib -Wl,-rpath,/opt/local/lib
make[2]: Leaving directory
`/opt/local/var/macports/build/_Users_chris_Projects_MacPorts_dports_science_geant4/geant4.10.0/work/build'
/opt/local/bin/cmake -E cmake_progress_report
/opt/local/var/macports/build/_Users_chris_Projects_MacPorts_dports_science_geant4/geant4.10.0/work/build/CMakeFiles
3
[ 6%] Built target G4analysis
make[1]: Leaving directory
`/opt/local/var/macports/build/_Users_chris_Projects_MacPorts_dports_science_geant4/geant4.10.0/work/build'
make: *** [all] Error 2
}}}
If I simply comment out the blacklist, and try again, the build proceeds
and finishes just fine.
So it appears, at least for OSX10.9, and geant4.10.0, the blacklist is too
restrictive, and is preventing use of the default clang compiler (which is
always the best one to use, if it works, I think), which works fine. I
haven't tested any other geant4 versions though, so perhaps others have
problems. If they do, then that shouldn't prevent the use of the system
clang with 10.0, and the blacklist should then be version specific...
Chris
--
Ticket URL: <https://trac.macports.org/ticket/42875#comment:14>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list