-
Notifications
You must be signed in to change notification settings - Fork 341
Adding VersionStream for rust-1.87 #53554
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
base: main
Are you sure you want to change the base?
Conversation
⚙️ Build Failed: Configuration
Build Details
Root Cause Analysis 🔍The build process tried to modify a configuration file (config.toml) that doesn't exist. This appears to be in the context of building Rust 1.87.0 from source. After the configure script ran successfully and created bootstrap.toml, it seems there was an attempt to modify config.toml with sed, but this file wasn't found. 🔍 Build failure fix suggestionsFound similar build failures that have been fixed in the past and analyzed them to suggest a fix: Suggested ChangesFile: melange.yaml
Replacement:
Click to expand fix analysisAnalysisThe build failure occurs because the build process is trying to modify a configuration file (config.toml) that doesn't exist at the specified location. Based on the error "sed: config.toml: No such file or directory", it appears that after the configure script runs, it's expected to create a config.toml file, but this file is either not being created or is being created in a different location than where the sed command is looking for it. In Rust's build system, the ./configure script typically generates a config.toml file in the project root. The current build pipeline runs the configure script successfully but when it attempts to modify the config.toml file in the subsequent step, the file cannot be found. This indicates a potential issue with the configure script's output or with the working directory when the sed command is executed. Click to expand fix explanationExplanationThe error occurs because the sed command is trying to modify a file (config.toml) that doesn't exist after the configure script runs. In Rust's build system, sometimes the configuration file is created as bootstrap.toml instead of config.toml, or the configure script might not be generating the expected config.toml file at all. The suggested fix addresses this issue by:
This approach ensures that the config.toml file exists before attempting to modify it with sed. Based on the error message and the build process flow, it appears that the configure script may be creating bootstrap.toml instead of config.toml, or not creating the config file at the expected location. The fix maintains the original intent of modifying the configuration to set "deny-warnings = false" while ensuring the file exists first. This is a common pattern in build systems where output file names might change between versions of the software being built. Click to expand alternative approachesAlternative Approaches
Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
Blocked on llvm-20 updates was able to build successfully with a local llvm-20
|
Signed-off-by: Ajay Kemparaj <[email protected]>
@ajayk As long as LLVM isn't updated to 20 #53354 I'm afraid Rust 1.87 can't be build 😅 |
No description provided.