• mexicancartel@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    “Patching incompatible software”

    What does that mean? If glibc is supported why there is a portability issueand requirement of patches?

      • mexicancartel@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        Well if glibc is supported all glibc softwares must work right?? Patching the software to support musl would not be needed if it does support glibc

      • mexicancartel@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 months ago

        I have checked the void website and it does NOT support glibc. Here is it:

        Wait edit: there is musl variant and glibc variant…

        Incompatible software

        musl practices very strict and minimal standard compliance. Many commonly used platform-specific extensions are not present. Because of this, it is common for software to need modification to compile and/or function properly. Void developers work to patch such software and hopefully get portability/correctness changes accepted into the upstream projects.

        Proprietary software usually supports only glibc systems, though sometimes such applications are available as flatpaks and can be run on a musl system. In particular, the proprietary NVIDIA drivers do not support musl, which should be taken into account when evaluating hardware compatibility.

        glibc chroot

        Software requiring glibc can be run in a glibc chroot.

      • 0x4E4F@lemmy.dbzer0.comOP
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        3 months ago

        Not just musl, software that depends on systemd (or parts of it) as well.

        We also need to patch binaries as well sometimes 😁. It is fun though, cutter and/or iaito are great tools.