Failure to build on MacOS due to missing `objectcopy`.

[a-rbts]

Despite binutils installed, the compilation on macos fails with objectcopy not found. Setting the path specifically as suggested doesn't seem to help either.

  Looking for "objcopy" or an equivalent tool

  --- stderr
  thread 'main' panicked at /Users/evariste/.cargo/git/checkouts/llama_cpp-rs-b9d51cabb4b43824/bc38e77/crates/llama_cpp_sys/build.rs:521:54:
  No suitable tool equivalent to "objcopy" has been found in PATH, if one is already installed, either add it to PATH or set OBJCOPY_PATH to its full path
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[pedro-devv]

What error shows up when you set OBJCOPY_PATH?

[a-rbts]

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)

[pedro-devv]

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.

[a-rbts]

Setting OBJCOPY_PATH to the full llvm-objcopy binary fixes the compilation errors. Thanks

[a-rbts]

Setting OBJCOPY_PATH to the full llvm-objcopy binary fixes the compilation errors. Thanks!

[bruceunx]

Same problem with macos + m2 chip, just brew install llvm and add path to environment to fix problem.