#50426 closed defect (fixed)
geant4.10.2: broken links of dylibs
Reported by: | mojca (Mojca Miklavec) | Owned by: | mojca (Mojca Miklavec) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | hapaguy (Brian Kurt Fujikawa) | |
Port: | geant4.10.2 |
Description
Due to lack of proper/extensive testing the new geant4.10.2 port appears to be broken:
---> Scanning binaries for linking errors Could not open /opt/local/lib/libG4zlib.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4clhep.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4global.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) Could not open /opt/local/lib/libG4intercoms.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4materials.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4graphics_reps.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4geometry.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4particles.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4track.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4digits_hits.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4processes.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4tracking.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4event.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) Could not open /opt/local/lib/libG4run.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4modeling.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib as broken Could not open /opt/local/lib/libG4vis_management.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4GMocren.dylib as broken Could not open /opt/local/lib/libG4FR.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4GMocren.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4GMocren.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4OpenGL.dylib as broken Could not open /opt/local/lib/libG4interfaces.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4OpenGL.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4OpenGL.dylib as broken Could not open /opt/local/lib/libG4gl2ps.dylib: Error opening or reading file (referenced from /opt/local/lib/Geant4/Geant4.10.2/libG4OpenGL.dylib) DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4OpenGL.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4RayTracer.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4Tree.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4VRML.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4analysis.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4digits_hits.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4error_propagation.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4event.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4geometry.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4gl2ps.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4global.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4graphics_reps.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4intercoms.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4interfaces.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4materials.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4modeling.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4parmodels.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4persistency.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4physicslists.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4processes.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4readout.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4run.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4track.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4tracking.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4visHepRep.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4visXXX.dylib as broken DEBUG: Marking /opt/local/lib/Geant4/Geant4.10.2/libG4vis_management.dylib as broken ---> Found 316 broken file(s), matching files to ports
Maybe the new version of Geant4 partially ignores the setting
-DCMAKE_INSTALL_LIBDIR=${prefix}/lib/Geant4/Geant${geant.version_simple}
but this needs more testing.
Change History (5)
comment:1 Changed 9 years ago by hapaguy (Brian Kurt Fujikawa)
Cc: | brian.fujikawa@… added |
---|
comment:2 Changed 9 years ago by mojca (Mojca Miklavec)
I have no idea how to debug this. I submitted a bug report here:
comment:3 Changed 9 years ago by mojca (Mojca Miklavec)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in r147160. The problem was that the cmake PortGroup automatically adds -DCMAKE_INSTALL_NAME_DIR=/opt/local/lib
and a few other settings which conflicted with -DCMAKE_INSTALL_LIBDIR=/opt/local/lib/Geant4/Geant4.10.2
. I hope this didn't break the older versions of Geant4. We probably need better support for these kind of scenarios in cmake-1.0.tcl
.
comment:4 Changed 8 years ago by RJVB (René Bertin)
Re: https://github.com/macports/macports-ports/pull/26#issuecomment-264447506
I think that with the current (my...) cmake-1.1.tcl you ought to be able to replace the setting for CMAKE_INSTALL_NAME_DIR
in configure.pre_args, and add the Geant libdir (${prefix}/lib/Geant4/Geant4.10.2) to cmake.install_rpath
.
I don't think this is a very common thing, but we *could* add an options variable for CMAKE_INSTALL_NAME_DIR
(which sets the string specifying the directory portion of the “install_name” field of shared libraries on Mac OSX to use in the installed targets.
).
comment:5 Changed 8 years ago by mojca (Mojca Miklavec)
Is there something I should test now? (Else I would prefer to do the changes once a new version gets released.)
Cc Me!