| 1 |
On 2018-01-28, Mart Raudsepp <leio@g.o> wrote: |
| 2 |
> On Sat, 2018-01-27 at 18:17 +0000, Richard Bradfield wrote: |
| 3 |
>> Hi folks, |
| 4 |
>> |
| 5 |
>> Forgive me if this has been spotted elsewhere, it's not in this list |
| 6 |
>> yet |
| 7 |
>> as far as I can see. |
| 8 |
>> |
| 9 |
>> The excellent work to bring the version of Rust in ~amd64 up to date |
| 10 |
>> has |
| 11 |
>> had an unfortunate side effect, in that it now prevents Firefox from |
| 12 |
>> building. Firefox appears to only supports Rust 1.19 and no later. |
| 13 |
>> |
| 14 |
>> I get a failure in one of the Rust components, as the build converts |
| 15 |
>> warnings to errors, and an import is now unused in 1.23 as it's now |
| 16 |
>> implicitly in scope, according to this thread [1] |
| 17 |
>> |
| 18 |
>> I know this is only a minor point release, but I was hoping to update |
| 19 |
>> for the SPECTRE mitigations. |
| 20 |
>> |
| 21 |
>> Has anyone patched this themselves, or do I need to think about |
| 22 |
>> rolling |
| 23 |
>> the system rust back to 1.19? |
| 24 |
>> |
| 25 |
>> Emerge build log is attached, it's a bit noisy around the errors |
| 26 |
>> sadly. |
| 27 |
>> |
| 28 |
>> |
| 29 |
>> [1] https://www.reddit.com/r/rust/comments/7rjvfu/this_is_why_you_sho |
| 30 |
>> uld_not_treat_warnings_as/ |
| 31 |
> |
| 32 |
> This is https://bugs.gentoo.org/645718 |
| 33 |
> |
| 34 |
> Hopefully the problem just goes away with firefox 58, which is |
| 35 |
> available in mozilla overlay and should get to main tree soon (last I |
| 36 |
> heard some build tests were still running before introduction to main |
| 37 |
> tree). |
| 38 |
> Though if warnings are treated as errors still there too, then it'll |
| 39 |
> hit again at some point, I guess, unless that bit is solved for good. |
| 40 |
> |
| 41 |
> |
Archives