[MacPorts] #52196: Consider not using @rpath for llvm and clang libraries
#52196: Consider not using @rpath for llvm and clang libraries ------------------------+------------------------------------------ Reporter: jeremyhu@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: llvm-3.8 llvm-3.9 llvm-devel ------------------------+------------------------------------------ We should consider not using @rpath for the newer llvm-3.8 and newer libraries. We probably will still want to keep libLTO as @rpath-relative such that ld64 will continue to use the version from the selected toolchain. -- Ticket URL: <https://trac.macports.org/ticket/52196> MacPorts <https://www.macports.org/> Ports system for macOS
#52196: Consider not using @rpath for llvm and clang libraries -------------------------------------------+------------------------ Reporter: jeremyhu@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: llvm-3.8 llvm-3.9 llvm-devel | -------------------------------------------+------------------------ Description changed by jeremyhu@…: Old description:
We should consider not using @rpath for the newer llvm-3.8 and newer libraries. We probably will still want to keep libLTO as @rpath-relative such that ld64 will continue to use the version from the selected toolchain.
New description: We should consider not using @rpath for the newer llvm-3.8 and newer libraries. We probably will still want to keep libLTO as @rpath-relative such that ld64 will continue to use the version from the selected toolchain. If not, then `llvm-config --ldflags` should be fixed to setup rpath. -- -- Ticket URL: <https://trac.macports.org/ticket/52196#comment:1> MacPorts <https://www.macports.org/> Ports system for macOS
participants (1)
-
MacPorts