-
Notifications
You must be signed in to change notification settings - Fork 13k
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
make check
fails on OSX
#10811
Comments
This should have been fixed by #10771. Are you using an older version of rust? |
I'm using a version from a few hours ago, and I've tried clobbering any local state with |
What revision are you using? |
@alexcrichton: I am also running into this error on OSX 10.9, on 1b12dca. |
This is a 10.9 error. You can work around it by removing -L $(TMPDIR) from tools.mk. However this is likely to break the build on other platforms. |
I think it's caused by Clang implicitly including the current directory as a link argument. Since there is no gcc on 10.9 anymore, this has started happening. |
@metajack: I think I found a proper fix. If you change |
Another option is to add --- a/src/test/run-make/tools.mk +++ b/src/test/run-make/tools.mk @@ -1,5 +1,5 @@ RUSTC := $(RUSTC) --out-dir $(TMPDIR) -L $(TMPDIR) -CC := $(CC) -L $(TMPDIR) +CC := $(CC) -Qunused-arguments -L $(TMPDIR) RUN = $(TMPDIR)/$(1) FAILS = $(TMPDIR)/$(1) && exit 1 || exit 0 |
This is probably not quite enough since this option doesn't seem to exist in gcc. Do we have a CFG variable that detects whether we're using clang or gcc? |
This modifies the `configure` to set `CFG_ENABLE_CLANG=1` if `gcc` is actually `clang`. This is needed because OS X's clang enables warning on unused command line arguments. Our build system suppresses this by default, but when `CFG_ENABLE_CLANGE=0`, we do not. This causes one of the tests to fail. This patch changes rust to directly use clang, which fixes the build failure. Closes #10811
[`match_wild_err_arm`]: do not lint in const contexts Fixes rust-lang#10635. changelog: [`match_wild_err_arm`]: do not lint in const contexts as `Result::{unwrap, expect}` is not const-stable
I get this error:
This patch seems to fix the problem for me: dwrensha@1693b81
The text was updated successfully, but these errors were encountered: