<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Riscv on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/riscv/</link>
    <description>Recent content in Riscv on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/riscv/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cross-Compiling in 2026: Zig vs crosstool-NG vs riscv-gnu-toolchain</title>
      <link>https://www.pistack.xyz/posts/2026-11-17-cross-compiling-zig-crosstool-ng-riscv-toolchain/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-17-cross-compiling-zig-crosstool-ng-riscv-toolchain/</guid>
      <description>&lt;p&gt;Cross-compiling is the task every build engineer underestimates exactly once. The binary compiles, it links, it copies to the target — and then it dies with &lt;code&gt;version &#39;GLIBC_2.34&#39; not found&lt;/code&gt;, because the toolchain on your build host was built against a newer C library than the machine you are deploying to. The failure is not in your code. It is in the toolchain, and it usually surfaces after the artifact has already been promoted.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
