-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Reconfiguring should preserve CFG_* settings #387
Comments
The way I deal with needing a special version of LLVM and Clang is to create an env.sh that I source in my terminal before beginning rust work. This changes to PATH so that the Rust-compatible LLVM and Clang are preferred over the system default. Of course, being able to specify a user config file that overrides the automatically determined values would be nice sometimes too. |
overriding CFG settings manually is not supported; landed support for hitting this particular case in different way |
Diff reduction between OpenBSD and Bitrig Bitrig had a number of errors and omissions. Also, fill out struct glob_t on all BSDs. A follow-up commit will condense OpenBSD/Bitrig common code into a separate file.
Attributes on functions
…1_17 Sync from rust 2023/11/17
As I mentioned in graydon/rust#368, I need to specify a custom version of llvm and clang for compiling rust. Unfortunately, when the makefiles are changed, this triggers a reconfigure, which blows away my CFG_* settings. This results in the wrong version of clang being used, which causes my build to error out. Could the CFG_ be preserved across reconfigures to prevent this from happening?
The text was updated successfully, but these errors were encountered: