GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)

Could you please add a test in github action to make sure we don't regress in the future?

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)

@Ecordonnier I don't know pkg names of Ubuntu well. Needs your help.

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)
Skipping an intermittent issue tests/tail/overlay-headers (passes in this run but fails in the 'main' branch)

you are mixing changes {} => () and the rest of the change
could you please rewrite the stack to have commits doing one change

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)
Skipping an intermittent issue tests/tail/overlay-headers (passes in this run but fails in the 'main' branch)

Can't you just remove CARGOFLAGS from the call which is building uudocs instead of adding a new variable for the target? I would expect that those CARGOFLAGS would be for the target build, not for tools which are compiled for the host architecture.

Can't you just remove CARGOFLAGS from the call which is building uudocs instead of adding a new variable for the target?

No. Because it would block reusing prebuilt crate caches from coreutils (at non-cross build).

Because it would block reusing prebuilt crate caches from coreutils

@aaron-ang Is uudoc changed by feat_selinux or feat_systemd_logind and removing them cause double build?