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

Fix build breakage with current rustc: #2060

Closed
wants to merge 1 commit into from
Closed

Conversation

glennw
Copy link
Member

@glennw glennw commented Nov 19, 2017

error: the crate bitflags is compiled with the panic strategy abort which is incompatible with this crate's strategy of unwind

error: aborting due to previous error

error: the crate bitflags is compiled with the panic strategy abort which is incompatible with this crate's strategy of unwind

error: aborting due to previous error

error: Could not compile gleam.


This change is Reviewable

error: the crate `bitflags` is compiled with the panic strategy `abort` which is incompatible with this crate's strategy of `unwind`

error: aborting due to previous error

error: the crate `bitflags` is compiled with the panic strategy `abort` which is incompatible with this crate's strategy of `unwind`

error: aborting due to previous error

error: Could not compile `gleam`.
@Gankra
Copy link
Contributor

Gankra commented Nov 19, 2017

@bors-servo r+

do you know what changed?

@bors-servo
Copy link
Contributor

📌 Commit f3a58bd has been approved by Gankro

@bors-servo
Copy link
Contributor

⌛ Testing commit f3a58bd with merge 67f0e70...

bors-servo pushed a commit that referenced this pull request Nov 19, 2017
Fix build breakage with current rustc:

error: the crate `bitflags` is compiled with the panic strategy `abort` which is incompatible with this crate's strategy of `unwind`

error: aborting due to previous error

error: the crate `bitflags` is compiled with the panic strategy `abort` which is incompatible with this crate's strategy of `unwind`

error: aborting due to previous error

error: Could not compile `gleam`.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/2060)
<!-- Reviewable:end -->
@glennw
Copy link
Member Author

glennw commented Nov 19, 2017

With stable rustc, trying to build release + master of WR gives the compile errors above.

I'm not really sure what changed to cause this - I haven't updated rustc, and I don't think any dependencies should have changed due to the Cargo.lock?

Anyone with knowledge of this stuff explain (a) why this happened now (b) If this is a reasonable workaround for now (I don't think it will break Gecko?) (c) If there is a better fix?

@glennw
Copy link
Member Author

glennw commented Nov 19, 2017

This is the last PR to merge, and it contains dependency updates #2032.

So I guess that's what caused the build breakage, but I don't understand how that got through CI if that's the case... 😕

@Gankra
Copy link
Contributor

Gankra commented Nov 19, 2017

@bors-servo r-

seeing fishy stuff locally

@glennw
Copy link
Member Author

glennw commented Nov 19, 2017

Closing while we try to diagnose this a bit further.

@glennw glennw closed this Nov 19, 2017
@Gankra
Copy link
Contributor

Gankra commented Nov 19, 2017

Running cargo clean seems to fix it and I have no idea why (but I guess that's why the CI is fine).

@glennw glennw deleted the fix-build branch November 19, 2017 21:29
@glennw
Copy link
Member Author

glennw commented Nov 19, 2017

OK, as @gankro identified, this seems to be some kind of rustc / cargo bug - running cargo clean locally and then building completes successfully. 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants