datenwolf<p>All I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>llvm</span></a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clang</span></a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>squashfs</span></a> image to carry around to my various development machines.</p><p>You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.</p><p>Yeah, about that. IYKYK</p>