On Tue, 13 Oct 2026 at 12:02, Etienne Cordonnier <[email protected]> wrote:
> > - investigate and propose a plan for pseudo compatibility. It's not > easy: pseudo relies on substituting libc API, and rust binaries issue > kernel syscalls directly. > > It is doable, since uutils-coreutils already uses the libc crate for many > things, and the rustix crate can be configured at build-time to use the > libc crate instead of using kernel syscalls directly. > On the other hand, PREFERRED_PROVIDER_coreutils is independent of > PREFERRED_PROVIDER_coreutils-native, and very few recipes depend on > coreutils-native, so I suggest decoupling a potential merge of > uutils-coreutils with pseudo support. The target version delivers almost > all the value, and pseudo compatibility can follow separately. Or am I > missing something? > It's not just about coreutils-native, it's about what implementation of coreutils is provided by host distributions. For now, the project has forced GNU coreutils on Ubuntu, but going forward this may not be sustainable: https://git.openembedded.org/openembedded-core/commit/?id=16f2684ebeffa72b5d90525cf9102751b68c298e and we'll either have to convince distros to build with libc crates, or do such a build ourselves via -native recipe. (note also all the fails that were observed when trying to use uutils from the ubuntu host, which means at least a year ago it was nowhere near mature) Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247715): https://lists.openembedded.org/g/openembedded-core/message/247715 Mute This Topic: https://lists.openembedded.org/mt/121685421/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
