<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compiler on icyveins7's blog</title><link>https://icyveins7.github.io/tags/compiler/</link><description>Recent content in Compiler on icyveins7's blog</description><generator>Hugo</generator><language>en-us</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 20 Oct 2025 20:00:00 +0800</lastBuildDate><atom:link href="https://icyveins7.github.io/tags/compiler/index.xml" rel="self" type="application/rss+xml"/><item><title>Build your own tools, gcc edition</title><link>https://icyveins7.github.io/posts/2025/10/build-your-own-tools-gcc-edition/</link><pubDate>Mon, 20 Oct 2025 20:00:00 +0800</pubDate><guid>https://icyveins7.github.io/posts/2025/10/build-your-own-tools-gcc-edition/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;Not complicated, but always good to know the process.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;In this series (?) I&amp;rsquo;ll cover something I always wanted to write down: compiling the toolchains/compilers I use from source. This means, specifically, no using of package managers i.e. not allowed to &lt;code&gt;sudo apt install&lt;/code&gt; dependencies. Of course, this has its limits (&lt;em&gt;you need a compiler to compile gcc, and some OSes don&amp;rsquo;t come pre-installed with one&lt;/em&gt;). However, the premise here is to at least be familiar with the minimal required dependencies, and where to get them (at the time of writing), and then what to do to build everything.&lt;/p&gt;</description></item></channel></rss>