Skip to content
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

Allow bootstrapping without a key. Fixes #36548 #37265

Merged
merged 1 commit into from
Oct 19, 2016
Merged

Conversation

brson
Copy link
Contributor

@brson brson commented Oct 19, 2016

This will make it easier for packagers to bootstrap rustc when they happen
to have a bootstrap compiler with a slightly different version number.

It's not ok for anything other than the build system to set this environment variable.

r? @alexcrichton

@brson brson added the beta-nominated Nominated for backporting to the compiler in the beta channel. label Oct 19, 2016
@brson
Copy link
Contributor Author

brson commented Oct 19, 2016

Nominating to get this convenience for packagers in their hand sooner. The backport will require changing the transitionary key.

@brson
Copy link
Contributor Author

brson commented Oct 19, 2016

cc @nagisa

@brson
Copy link
Contributor Author

brson commented Oct 19, 2016

Oh I see a problem with this patch that makes me wonder how it's building successfully...

This will make it easier for packagers to bootstrap rustc when they happen
to have a bootstrap compiler with a slightly different version number.

It's not ok for anything other than the build system to set this environment variable.
@brson
Copy link
Contributor Author

brson commented Oct 19, 2016

OK, fixed. The answer to how it was building successfully is that there are two build systems.

@alexcrichton
Copy link
Member

@bors: r+ p=1

Higher priority as we're likely to backport this.

@bors
Copy link
Contributor

bors commented Oct 19, 2016

📌 Commit d3c5905 has been approved by alexcrichton

cmd.env("RUSTC_BOOTSTRAP_KEY", bootstrap_key);
fn add_bootstrap_key(&self, cmd: &mut Command) {
cmd.env("RUSTC_BOOTSTRAP", "");
// FIXME: Transitionary measure to bootstrap using the old bootstrap logic.
Copy link
Member

Choose a reason for hiding this comment

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

This should be SNAP, I think? I don’t think anybody looks at FIXMEs on a rollover (though I suspect nobody looks at SNAPs either anymore?)

@nagisa
Copy link
Member

nagisa commented Oct 19, 2016

Seems good to me.

eddyb added a commit to eddyb/rust that referenced this pull request Oct 19, 2016
Allow bootstrapping without a key. Fixes rust-lang#36548

This will make it easier for packagers to bootstrap rustc when they happen
to have a bootstrap compiler with a slightly different version number.

It's not ok for anything other than the build system to set this environment variable.

r? @alexcrichton
@bors
Copy link
Contributor

bors commented Oct 19, 2016

⌛ Testing commit d3c5905 with merge 2918ab8...

eddyb added a commit to eddyb/rust that referenced this pull request Oct 19, 2016
Allow bootstrapping without a key. Fixes rust-lang#36548

This will make it easier for packagers to bootstrap rustc when they happen
to have a bootstrap compiler with a slightly different version number.

It's not ok for anything other than the build system to set this environment variable.

r? @alexcrichton
@bors
Copy link
Contributor

bors commented Oct 19, 2016

⛄ The build was interrupted to prioritize another pull request.

bors added a commit that referenced this pull request Oct 19, 2016
@bors bors merged commit d3c5905 into rust-lang:master Oct 19, 2016
@bluss bluss added the relnotes Marks issues that should be documented in the release notes of the next release. label Oct 19, 2016
cuviper added a commit to cuviper/rust that referenced this pull request Oct 19, 2016
A new point-release shouldn't change any language semantics, so a local
stage0 that matches MAJOR.MINOR version should still be considered a
local-rebuild as far as `--cfg stageN` features go.

e.g. `1.14.0` should be considered a local-rebuild for any `1.14.X`.

(Bootstrap keys used to be an issue too, until rust-lang#37265.)
bors added a commit that referenced this pull request Oct 20, 2016
Detect local-rebuild by just the MAJOR.MINOR version

A new point-release shouldn't change any language semantics, so a local
stage0 that matches MAJOR.MINOR version should still be considered a
local-rebuild as far as `--cfg stageN` features go.

e.g. `1.14.0` should be considered a local-rebuild for any `1.14.X`.

(Bootstrap keys used to be an issue too, until #37265.)
@brson brson removed the relnotes Marks issues that should be documented in the release notes of the next release. label Oct 24, 2016
@alexcrichton alexcrichton added the beta-accepted Accepted for backporting to the compiler in the beta channel. label Oct 24, 2016
@brson brson mentioned this pull request Nov 3, 2016
the-kenny added a commit to NixOS/nixpkgs that referenced this pull request Nov 28, 2016
Newer nightlies check a new environment variable that if set will loosen
restrictions on which compiler version can be used for bootstrapping.

Upstream issue is at rust-lang/rust#37265
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beta-accepted Accepted for backporting to the compiler in the beta channel.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants