-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linker on macOS prints excessive warnings in CI #15130
Comments
We might want to try using a new version of LLVM (#14651). |
Updating to LLVM 18.1 does not make the warnings go away. Was worth a try 🤷 |
For what it's worth, I'm getting this locally again with 1.14 on an arm mac on macos 15.1 |
XCode in CI is outdated, maybe updating that would help? Could someone try the compiler build from #15164 to check if it still produces warnings? |
Interestingly enough I'm on 1.14 on an arm mac on macos 15.1 and I'm not currently having any problems. @will what xcode version are you on? I'm apparently on 16.1 installed via EDIT: $ xcode-select -p
/Library/Developer/CommandLineTools
$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables | grep version
version: 16.1.0.0.1.1729049160 |
@Blacksmoke16 I'm on 15.1 and this is what I'm seeing for xcode:
|
I could get this on |
FWIW, I was able to resolve the warnings with the following:
I don't have much more to offer on this one at this time, but figured I'd mention it just in case it helped lead to a proper solution. However, here are some of the other details of my setup:
|
The linker on macOS prints such as warning for every individual object file:
Example CI run: https://github.com/crystal-lang/crystal/actions/runs/11521615235/job/32075666471?pr=15127
The log is spammed with about ~87k of these warnings, which is just excessive. It's basically unusable through the GitHub web UI. You can still download the entire job log as a text file.
Anyway, we should not get that many warnings.
Ideally, we need to fix this. Or at least silence the warnings.
I'm not familiar with macOS build system, so I'm not sure what this warning even means or what we're suppose to do.
This has previously been mentioned in #14835
The text was updated successfully, but these errors were encountered: