Skip to content

mk/rt: "export CC" does not seem to work (gcc observed), use explicit shell variables instead #18194

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

Merged
merged 1 commit into from
Oct 21, 2014

Conversation

codyps
Copy link
Contributor

@codyps codyps commented Oct 20, 2014

This was run into while attempting to integrate rust with bitbake's build system. I expect it's caused by some other environment variables being set to gcc but didn't track down the exact cause myself.

@rust-highfive
Copy link
Contributor

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

bors added a commit that referenced this pull request Oct 21, 2014
This was run into while attempting to integrate rust with bitbake's build system. I expect it's caused by some other environment variables being set to gcc but didn't track down the exact cause myself.
@bors bors closed this Oct 21, 2014
@bors bors merged commit d75ff2f into rust-lang:master Oct 21, 2014
@codyps codyps deleted the libbacktrace-env branch May 24, 2015 20:22
lnicola pushed a commit to lnicola/rust that referenced this pull request Oct 8, 2024
…eykril

minor: Stricter requirements for package wide flycheck

Require the existence of a target and `check_workspace` to be false to restart package-wide flycheck. Fixes rust-lang#18194 , rust-lang#18104
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants