Skip to content

Conversation

@GuillaumeGomez
Copy link
Member

Last sync we lost some time remembering we needed to update build-gccjit.sh. I don't think there is any reason to not copy the file inside the Dockerfile so here it is.

cc @antoyo
r? @Kobzol

@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-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jan 14, 2025
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer
Copy link
Collaborator

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@Kobzol
Copy link
Member

Kobzol commented Jan 14, 2025

Hmm, I wonder how this will interact with Docker caching. Actually, I have a PR mostly ready that builds GCC from tree, after which we could remove build-gccjit.sh altogether, I hope.

@GuillaumeGomez
Copy link
Member Author

😮 That's much better than this hack!
Then let's close this.

@GuillaumeGomez GuillaumeGomez deleted the gcc-backend-sync branch January 14, 2025 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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-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.

4 participants