Closed a-rbts closed 7 months ago
What error shows up when you set OBJCOPY_PATH
?
It cannot execute it. I don't think objcopy is meant to be used in the macos process.
--- stderr
/Users/evariste/usr/bin/objcopy: /Users/evariste/usr/bin/objcopy: cannot execute binary file
thread 'main' panicked at /Users/evariste/.cargo/git/checkouts/llama_cpp-rs-b9d51cabb4b43824/bc38e77/crates/llama_cpp_sys/build.rs:418:13:
An error as occurred while modifying global symbols from library file (exit status: 126)
I see, you might be right about binutils
's objcopy
on MacOS, I'll have to change the error message depending on OS. Try installing a recent version LLVM and using llvm-objcopy
, that should work.
Setting OBJCOPY_PATH to the full llvm-objcopy binary fixes the compilation errors. Thanks
Setting OBJCOPY_PATH to the full llvm-objcopy binary fixes the compilation errors. Thanks!
Same problem with macos + m2 chip, just brew install llvm and add path to environment to fix problem.
Despite
binutils
installed, the compilation on macos fails with objectcopy not found. Setting the path specifically as suggested doesn't seem to help either.