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
cmd/dist: depends on clang license being accepted on OSX #13099
Comments
It seems kind of special purpose to have cmd/dist print out a specific message about this oddity. What does clang print if you run it as non-root before root? Would it be sufficient for cmd/dist to display that output? |
It prints out a message to the effect that clang needs to be run as root to accept the license (I've lost the output, so I can't give exact details.) I was just thinking that it would make sense for the build process to make it clear what the problem was. Either by outputting clang's output, or by printing a message when darwin's clang fails with a certain error code. |
It prints out
As an experienced user, I knew what I had to do. But it is confusing for anyone who doesn't know they need to run clang, accept the license and so on. |
It's wacky but I think we probably do need to special case it. OS X is a very common platform for our users, and this is a very common situation. Printing the compiler output is not enough unless we make it very clear that it's compiler output and that the user is not being asked to sudo ./all.bash (which would work but isn't what we want). |
On a fresh Capitan (10.11.1 (15B42)) install, I see:
|
@bradfitz That must be before you installed Xcode. After you install Xcode then you get the message about re-running as root. |
CL https://golang.org/cl/17940 mentions this issue. |
In a recent update to either the OS or the dev-tools clang on OSX will refuse to run (with error code 69) until it is run as root, and the license is accepted.
The output from ./all.bash when compiling from source is:
Which is a little of a head scratcher. I think the error message could elaborate on a possible cause, so that the users don't think the only solution is to disable cgo.
The text was updated successfully, but these errors were encountered: