Changes between Initial Version and Version 2 of Ticket #70404


Ignore:
Timestamp:
Jul 19, 2024, 4:50:34 PM (2 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

The way that rpath works on macOS is that when you link with a library that uses rpath, you have to supply a linker flag to tell it what @rpath should expand to. Looks like our llvm ports have been using @rpath for libLLVM.dylib for a long time, so if old versions worked without you having to specify the rpath manually, maybe that's something that can be fixed in the new llvm versions. Until then, you can do it manually, for example by using the linker flag -rpath /opt/local/libexec/llvm-18/lib.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #70404

    • Property Keywords llvm-18 removed
    • Property Cc cjones051073 jeremyhu added
    • Property Port llvm-18 llvm-devel added
    • Property Summary changed from Link with with llvm-18 to llvm-18: libLLVM.dylib not loaded at runtime

  • Ticket #70404 – Description

    initial v2  
    1 My project using llvm-18 correctly build but I get this error at runtime: Library not loaded: '@rpath/libLLVM.dylib'
    2 The same happens with llvlm-devel and the project is correctly working with llvm-17. 
     1My project using llvm-18 correctly build but I get this error at runtime:
     2{{{
     3Library not loaded: '@rpath/libLLVM.dylib'
     4}}}
     5The same happens with llvm-devel and the project is correctly working with llvm-17.