| Summary: | dev-lang/rust-1.37.0 arm keyword request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Flogeras <dflogeras2> |
| Component: | Keywording | Assignee: | Gentoo Rust Project <rust> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aos, herrtimson, jstein |
| Priority: | Normal | Keywords: | KEYWORDREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
David Flogeras
2019-10-06 13:01:47 UTC
The rust team has been very unresponsive about adding arm keywords, at least the ebuilds themselves are working. Mind you, rust-1.38 was shipped with broken armv7, and firefox as the possible main consumer can't be built with -j1 anymore. That would affect only stable keywords in my interpretation, but you also might want to just get along with the unkeyworded ebuilds. upstream provides only the following arm bootstrap-capable tarballs: armv6 (softfloat and hardfloat) armv7-hardfloat it's possible to ~arm it certainly, and mask it in lesser sub-profiles but it'll not get stable keywords ever, so don't count on it. I will look at it once I get arm box up, you know how much time it takes. multiple by number of profiles, it adds up quickly. I have to test it on all arches/profiles/ssl/useflag combos we support before I release it, because it's brittle sometimes. also to ensure it actually works I usually build firefox with it to ensure it actually works. so build times are horrible. throwing in at least 3 arm builds each taking hours to complete is not something I'd enjoy, but if it's ~arm and you report breakage right away I can bump it blindly leaving ~arm build untested. what's broken in 1.38 by the way? That sounds good, but also feel free to close if it is not worth the time-sink at this point. My thinking was that even if it is ~arm (and not stable), that's less of a barrier to newer users to try to get firefox up and running. If at the very least this puts more eyes, and more bug reports to upstream it might be beneficial to the ecosystem as a whole. If not, I'm happy to continue unmasking myself. Especially if every second release is going to break and make trouble. rust-1.38.0 is broken on armv7 when compiling in --release mode, there's a fix in master which is on it's way to get backported into rust-1.39.0 beta https://github.com/rust-lang/rust/pull/65302 mind you, it would be sufficent to get rust-bin and virtual/rust keyworded, and eselect-rust of course. also there's no need to compile firefox nativly on an arm device, just to test if the rustc binary works. emerge --oneshot cbindgen followed by cbindgen -V should be sufficent for keywording. 1.38 and 1.40 are now arm keyworded, but without masks. feel free to reopen if something is wrong. |
