GCC Goes For "libc Diversity" With Picolibc Support

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67050

    GCC Goes For "libc Diversity" With Picolibc Support

    Phoronix: GCC Goes For "libc Diversity" With Picolibc Support

    Keith Packard is known for his X.Org/X11 work over the course of many years but alongside other software projects he also maintains Picolibc as a C library designed for embedded 32-bit and 64-bit systems. Recently he sent out a patch for adding Picolibc support to the GCC compiler...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • MastaG
    Senior Member
    • May 2012
    • 430

    #2
    Back in the days I used to experiment with uclibc and came to the conclusion that lots of GNU software assumes you're using glibc.
    Using something else will break things due to missing functionality.

    Comment

    • bug77
      Senior Member
      • Dec 2009
      • 6470

      #3
      I am wondering if we're not past the point where ISO C would also need to define some profiles for various purpose libs. I understand the difference and they're technically unrelated. They're still used together almost all the time.

      Comment

      • edxposed
        Senior Member
        • Jan 2023
        • 301

        #4
        The diversity of GNU is like the diversity of OS that Apple Arm products are able to run.

        Comment

        • caligula
          Senior Member
          • Jan 2014
          • 3307

          #5
          Originally posted by MastaG View Post
          Back in the days I used to experiment with uclibc and came to the conclusion that lots of GNU software assumes you're using glibc.
          Using something else will break things due to missing functionality.
          Now a days there's musl which supports more apps. There are some political issues though, like the fact that musl and systemd aren't compatible (musl devs doesn't want to support systemd and systemd dev don't want to support anything other than glibc), which makes things a bit hard because most distros now use systemd.

          Comment

          • bug77
            Senior Member
            • Dec 2009
            • 6470

            #6
            Originally posted by caligula View Post

            Now a days there's musl which supports more apps. There are some political issues though, like the fact that musl and systemd aren't compatible (musl devs doesn't want to support systemd and systemd dev don't want to support anything other than glibc), which makes things a bit hard because most distros now use systemd.
            Tbh, it makes zero sense for a C lib such as musl (or glibc) to support something like systemd. Luckily, Alpine doesn't use systemd, so I don't care whether systemd is tied to glibc or not.

            Comment

            • brad0
              Senior Member
              • May 2012
              • 1000

              #7
              Originally posted by caligula View Post
              musl devs doesn't want to support systemd
              That's not how anything should work.

              Comment

              • mobadboy
                Senior Member
                • Jul 2024
                • 160

                #8
                too woke for me, sorry

                Comment

                • NekkoDroid
                  Junior Member
                  • Feb 2024
                  • 42

                  #9
                  Originally posted by caligula View Post
                  musl devs doesn't want to support systemd and systemd dev don't want to support anything other than glibc
                  From my knowledge it's more that systemd uses kernel APIs that glibc wraps that musl doesn't want to implement and systemd isn't gonna make their own wrappers when glibc already does the job.

                  Comment

                  • Weasel
                    Senior Member
                    • Feb 2017
                    • 4419

                    #10
                    Originally posted by NekkoDroid View Post
                    From my knowledge it's more that systemd uses kernel APIs that glibc wraps that musl doesn't want to implement and systemd isn't gonna make their own wrappers when glibc already does the job.
                    Sounds like systemd can suck it.

                    Comment

                    Working...
                    X