On 3/15/22 19:58, Peter Maydell wrote:
This results in every "Linking" step on my macos box producing the
warning:
ld: warning: directory not found for option
'-Lns/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0'
This was reported already back in January with Meson 0.59:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg861435.html
1. Linker has corrupted paths to clang directory (happens on all macOS
versions).
Monterey:
[732/737] Linking target qemu-system-mips-unsigned
ld: warning: directory not found for option
'-Lns/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0'
[733/737] Linking target qemu-system-mips64-unsigned
ld: warning: directory not found for option
'-Lns/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.0.0'
[737/737] Generating qemu-system-mips64 with a custom command
Catalina:
ld: warning: directory not found for option
'-Lveloper/CommandLineTools/usr/lib/clang/11.0.0'
[102/105] Linking target qemu-system-or1k-unsigned
ld: warning: directory not found for option
'-Lveloper/CommandLineTools/usr/lib/clang/11.0.0'
[104/105] Linking target qemu-system-ppc-unsigned
ld: warning: directory not found for option
'-Lveloper/CommandLineTools/usr/lib/clang/11.0.0'
[105/105] Generating qemu-system-ppc with a custom command
Roman, was this ever debugged? Is the broken path to the clang
directory included in build.ninja or is this a clang bug that somehow
has been latent so far?
Paolo
