Conversation
Now that uutils#11428 was merged, this should be fine. However, CI will still fail. See discussion on uutils#5297 (comment) for a potential fix. Compiling `cross` from git will cost 1m 31s on a 2014 Intel® Core™ i5-4210U CPU @ 1.70GHz (4)
|
GNU testsuite comparison: |
|
The expected failure on |
|
Plese resrtict building cross to netbsd by |
Ok, lets try that. |
|
GNU testsuite comparison: |
|
Are you ok with bumping MSRV from 1.88 to 1.92? Or should I do this only for NetBSD? EDIT: Maybe not ... I'll restrict this to the NetBSD build. |
|
MSRV bump should be traced at different issue. |
|
GNU testsuite comparison: |
|
@oech3 I cannot see how the CodSpeed benchmark service connection failure could be related to this PR. |
Are you saying I should create a new issue that states we need at least 1.92 to build |
|
This PR closes #5297 |
|
can be done at different PR, but we need to gate this by coreutils/.github/workflows/CICD.yml Lines 603 to 608 in e0f0318 which could cause another toolchain issue. |
|
Thanks! |
Ok, coming soon |
|
GNU testsuite comparison: |
|
All checks have passed @oech3, @cakebaker |
|
OK for me.
|
|
@sylvestre I hope it's clear now and that you are fine with it. Unfortunately, it seems |
|
GNU testsuite comparison: |
|
@0323pin I was going to ask why this requires Rust 1.92, but since you (and @he32) maintain the |
This comment was marked as resolved.
This comment was marked as resolved.
|
@xtqqczze As @oech3 pointed out, the reason is That said, this only affects the CI, native builds don't need the workaround. pkgsrc is currently in commit freeze ahead of branching stable and has Rust-1.91.1 but, all my builds were done using 1.94.0 |
|
I'm ok |
Now that #11428 was merged, this should be fine.
However, CI will still fail.
See discussion on #5297 (comment) for a potential fix.
Compiling
crossfrom git will cost 1m 31s on a 2014 Intel® Core™ i5-4210U CPU @ 1.70GHz (4)