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

Update emscripten #230

Merged
merged 1 commit into from
Aug 28, 2019
Merged

Update emscripten #230

merged 1 commit into from
Aug 28, 2019

Conversation

CryZe
Copy link
Contributor

@CryZe CryZe commented Nov 13, 2018

rustc switched to emscripten with LLVM 6. emscripten versions with LLVM 4 are not supported anymore. This upgrades emscripten to the same version as rustc is using in its CI.

rustc switched to emscripten with LLVM 6. emscripten versions with LLVM 4 are not supported anymore. This upgrades emscripten to the same version as rustc is using in its CI.
@Dylan-DPC-zz
Copy link

Thanks @CryZe

bors: try

bors bot added a commit that referenced this pull request Nov 13, 2018
@Dylan-DPC-zz
Copy link

bors: try

@bors
Copy link
Contributor

bors bot commented Nov 13, 2018

try

Not awaiting review

@bors
Copy link
Contributor

bors bot commented Nov 14, 2018

try

Build failed

@CryZe
Copy link
Contributor Author

CryZe commented Nov 14, 2018

So it seems like there's some spurious errors in here. But there's an actual problem with my PR in that the CI uses an old rust compiler for the wasm32-unknown-emscripten target due to rust-lang/cargo#4689

@Disasm Disasm added the S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work. label Feb 23, 2019
@CryZe
Copy link
Contributor Author

CryZe commented Mar 13, 2019

I would want this to be fixed, but in order for that to happen, the rustc version in the test needs to be bumped. However it is explicitly set to an old version, because cargo run is apparently broken with emscripten files in more recent rust versions. Can I just kill the cross run for the emscripten target and then this can be merged or how should this progress? (I find it highly unlikely that anyone fixes this problem on rust's side anytime soon as the emscripten targets are close to being unsupported with the verge of the unknown target. And cross's emscripten targets are completely broken until then if this isn't merged).

@CryZe
Copy link
Contributor Author

CryZe commented Apr 18, 2019

Can somebody tell me if I can just remove the tests for that target? The target is on the verge of dying anyway, so it's unlikely that anyone fixes the test runner bugs anytime soon. So I'd rather have this merged without the tests running than the target being broken on cross' side altogether.

@reitermarkus
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request Aug 27, 2019
230: Update emscripten r=reitermarkus a=CryZe

rustc switched to emscripten with LLVM 6. emscripten versions with LLVM 4 are not supported anymore. This upgrades emscripten to the same version as rustc is using in its CI.

Co-authored-by: Christopher Serr <[email protected]>
@bors
Copy link
Contributor

bors bot commented Aug 27, 2019

Timed out

1 similar comment
@bors
Copy link
Contributor

bors bot commented Aug 27, 2019

Timed out

@reitermarkus
Copy link
Member

bors retry

bors bot added a commit that referenced this pull request Aug 28, 2019
230: Update emscripten r=reitermarkus a=CryZe

rustc switched to emscripten with LLVM 6. emscripten versions with LLVM 4 are not supported anymore. This upgrades emscripten to the same version as rustc is using in its CI.

Co-authored-by: Christopher Serr <[email protected]>
@bors
Copy link
Contributor

bors bot commented Aug 28, 2019

Build succeeded

@bors bors bot merged commit 01d2be0 into cross-rs:master Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-blocked Status: marked as blocked ❌ on something else such as an RFC or other implementation work.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants