Skip to content

Conversation

@bjorn3
Copy link
Member

@bjorn3 bjorn3 commented Jan 27, 2026

No description provided.

@rustbot rustbot added 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) labels Jan 27, 2026
@rustbot
Copy link
Collaborator

rustbot commented Jan 27, 2026

r? @clubby789

rustbot has assigned @clubby789.
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


// Environment variables *required* throughout the build
//
// FIXME: should update code to not require this env var
Copy link
Contributor

@clubby789 clubby789 Jan 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this FIXME be moved/removed, or does 'this env var' refer to all of these? 🤔

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it also refers to CFG_COMPILER_BUILD_TRIPLE and maybe CFG_RELEASE_CHANNEL.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just went through the history. This fixme originates from the initial commit of the rust version of the build system and back then only applied to CFG_COMPILER_HOST_TRIPLE. The other env vars didn't exist yet. As such I removed the todo.

@clubby789
Copy link
Contributor

LGTM, but it could be good to update the fixme to 'these env vars' if that's appropriate; r=me when green with or without

This lint is allowed by default nowadays.
Rustc no longer depends on winapi. Only cg_clif, cg_gcc and rustfmt
still use it, none of which are libraries to compile against. And in
case of both cg_clif and cg_gcc it never ends up in an artifact we ship.
For cg_clif it only shows up when the jit mode is enabled, which is not
the case for the version we ship. For cg_gcc it is used by a test
executable, which isn't shipped either.
These flags should be available on the bootstrap compiler.
@bjorn3 bjorn3 force-pushed the remove_unnecessary_flags branch from e0b76a3 to 257ea3b Compare January 27, 2026 16:18
@bjorn3
Copy link
Member Author

bjorn3 commented Jan 27, 2026

Removed the --check-cfg change. Some tests produce warnings otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants