Skip to content

{aarch64,x86_64}-*-windows-gnullvm: build host tools #140772

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

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

mati865
Copy link
Member

@mati865 mati865 commented May 7, 2025

This will require MCP, but I suppose we need to know how long it takes to build first.

I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.

--enable-full-tools for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.

Almost every commit is self-contained, so let me know if I should split them into separate PRs.

try-job: dist-aarch64-windows-gnullvm
try-job: dist-x86_64-windows-gnullvm

@rustbot
Copy link
Collaborator

rustbot commented May 7, 2025

r? @marcoieni

rustbot has assigned @marcoieni.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels May 7, 2025
@rustbot
Copy link
Collaborator

rustbot commented May 7, 2025

This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp.

@mati865
Copy link
Member Author

mati865 commented May 11, 2025

Forgot to include try-job. Fixed it.

@marcoieni
Copy link
Member

This will require MCP, but I suppose we need to know how long it takes to build first.

ok, so I guess we need to try this, right?

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request May 15, 2025
{aarch64,x86_64}-*-windows-gnullvm: build host tools

This will require MCP, but I suppose we need to know how long it takes to build first.

I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.

`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.

Almost every commit is self-contained, so let me know if I should split them into separate PRs.

try-job: dist-windows-gnullvm
@bors
Copy link
Collaborator

bors commented May 15, 2025

⌛ Trying commit d0b81ca with merge 9772d67...

@rust-log-analyzer

This comment has been minimized.

@marcoieni
Copy link
Member

maybe you need to add the job to the src/ci/github-actions/jobs.yml file?

@bors
Copy link
Collaborator

bors commented May 15, 2025

💥 Test timed out

@mati865
Copy link
Member Author

mati865 commented May 15, 2025

Oh, right. Totally forgot about it.

@marcoieni
Copy link
Member

@bors try

@bors
Copy link
Collaborator

bors commented May 16, 2025

⌛ Trying commit b256449 with merge 34c404a...

bors added a commit to rust-lang-ci/rust that referenced this pull request May 16, 2025
{aarch64,x86_64}-*-windows-gnullvm: build host tools

This will require MCP, but I suppose we need to know how long it takes to build first.

I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.

`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.

Almost every commit is self-contained, so let me know if I should split them into separate PRs.

try-job: dist-windows-gnullvm
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 16, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 16, 2025
@mati865
Copy link
Member Author

mati865 commented May 16, 2025

System.IO.IOException: No space left on device

Unfortunately, free CI runners are not as capable as I had hoped. I've split the jobs now, but dunno if this will be acceptable.

@marcoieni
Copy link
Member

I've split the jobs now, but dunno if this will be acceptable.

yes, we prefer multiple free runner compared to 1 large runner 👍

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request May 19, 2025
{aarch64,x86_64}-*-windows-gnullvm: build host tools

This will require MCP, but I suppose we need to know how long it takes to build first.

I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.

`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.

Almost every commit is self-contained, so let me know if I should split them into separate PRs.

try-job: dist-aarch64-windows-gnullvm
try-job: dist-x86_64-windows-gnullvm
@bors
Copy link
Collaborator

bors commented May 19, 2025

⌛ Trying commit a84e84e with merge 9e708f5...

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 19, 2025

💔 Test failed - checks-actions

@marcoieni
Copy link
Member

@bors try

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 19, 2025

💔 Test failed - checks-actions

@mati865
Copy link
Member Author

mati865 commented May 19, 2025

Sorry, hoped that I can avoid another local run, but I made too many mistakes when splitting. It's fixed now.

@marcoieni
Copy link
Member

No worries!

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request May 19, 2025
{aarch64,x86_64}-*-windows-gnullvm: build host tools

This will require MCP, but I suppose we need to know how long it takes to build first.

I opted for bootstrapping from Linux because that's the easiest host system to work with, but once this hits beta, having dedicated Windows runners would be sensible and probably preferable.

`--enable-full-tools` for whatever reason doesn't seem to work when cross-compiling, because LLVM tools for the new hosts are not copied into the expected directory. And WiX that bootstrap relies upon to create .msi installers only supports Windows. I haven't tried, but it might be usable via Wine.

Almost every commit is self-contained, so let me know if I should split them into separate PRs.

try-job: dist-aarch64-windows-gnullvm
try-job: dist-x86_64-windows-gnullvm
@bors
Copy link
Collaborator

bors commented May 19, 2025

⌛ Trying commit e2f8e7f with merge 98bb621...

@bors
Copy link
Collaborator

bors commented May 19, 2025

☀️ Try build successful - checks-actions
Build commit: 98bb621 (98bb6215bc277dce97b5d4e1f271444dbbea04f0)

@marcoieni
Copy link
Member

timings look good 👍
image
so I guess this requires a MCP as you said in your first post, right? So I won't approve this PR yet.

@mati865
Copy link
Member Author

mati865 commented May 20, 2025

Thanks, I suppose the times will be even shorter with warm sccache.

@rustbot author

@rustbot
Copy link
Collaborator

rustbot commented May 20, 2025

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@rustbot rustbot added the A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. label May 31, 2025
mati865 added a commit to mati865/rust that referenced this pull request May 31, 2025
…ndows

This obviously doesn't work when cross-compiling from Linux.

Split out from: rust-lang#140772
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request May 31, 2025
…, r=jieyouxu

Fixes for building windows-gnullvm hosts

Split out from: rust-lang#140772
rust-timer added a commit that referenced this pull request May 31, 2025
Rollup merge of #141819 - mati865:windows-gnullvm-host-fixes, r=jieyouxu

Fixes for building windows-gnullvm hosts

Split out from: #140772
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants