<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Libc on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/libc/</link>
    <description>Recent content in Libc on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/libc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux libc Alternatives: musl vs glibc vs uClibc-ng vs diet libc</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-linux-libc-alternatives-musl-glibc-uclibc-ng-diet/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-linux-libc-alternatives-musl-glibc-uclibc-ng-diet/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every Linux binary — from the kernel&amp;rsquo;s init process to your web server — links against a C standard library (libc). This library provides the fundamental APIs for memory allocation, file I/O, string manipulation, threading, and system call interfaces. While most distributions default to &lt;strong&gt;glibc&lt;/strong&gt; (GNU C Library), several alternative C libraries offer different tradeoffs in binary size, performance, static linking, and security hardening.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
