![]() ![]() I'm trying to understand which AppleClang version people working on Mojave would typically have (also to decide which combination of OS and compiler we should support/test in our own projects). So when you say the newer one in Xcode above, you mean XCode 11.3, which you also have to download manually? ![]() I just thought Apple might be handing out more recent updates for XCode and not CLT. In retrospect that makes sense of course. But after installing Xcode 10.3 (which is maybe the latest version you get via softwareupdate?), it's still the same linker version 450. So I first thought from the comment above it is different if I install Xcode. I'm trying to understand in which cases you get the newer linker version > 450 on Mojave. That's the difference I think between our setups. Ok, so for you it is using ld from the CLT rather than the newer one in Xcode. There is a difference for C++17 features that werent available in AppleClang 10, but in 11, like full std::filesystem support, and the CLT upgrade broke our builds. the library features it thinks are available, even if you use the same libc++ from homebrew (llvm version 10). So CLT 11.3 actually caused some problems b/c AppleClang 11 somehow behaves differently to AppleClang 10 w.r.t. Run `brew link` on Homebrew's sbin was not found in your PATH but you have installedįormulae that put executables in /usr/local/sbin.Ĭonsider setting the PATH for example like so:Įcho 'export PATH="/usr/local/sbin:$PATH"' > ~/.bash_profile Those kegs to fail to run properly once built. Leaving kegs unlinked can lead to build-trouble and cause brews that depend on Warning: You have unlinked kegs in your Cellar. usr/local/include/python3.7m/greenlet/greenlet.h usr/local/include/python2.7/greenlet/greenlet.h If you didn't put them there on purpose they could cause problems whenīuilding Homebrew formulae, and may need to be deleted. Warning: Unbrewed header files were found in /usr/local/include. Working fine: please don't worry or file an issue just ignore this. Please note that these warnings are just used to help the Homebrew maintainers ![]() This is how I've tried to use clang-10 after installing it with brew: Command output /usr/local/opt/llvm/bin/clang-10 -isysroot `xcrun -show-sdk-path` file.cĬlang-10: error: linker command failed with exit code 1 (use -v to see invocation) I have been able to install it successfully, but the clang binary is broken. if brew gist-logs didn't work: ran brew config and brew doctor and included their output with your issue?.ran brew gist-logs (where is the name of the formula that failed) and included the output link?.ran brew doctor, fixed all issues and can still reproduce the problem?.ran brew update and can still reproduce the problem?.If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again. Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |