From e0ab3f257d16b950cceb3cc89e1a6c6cebdb9f48 Mon Sep 17 00:00:00 2001
From: EsotericDryad <63485553+EsotericDryad@users.noreply.github.com>
Date: Sun, 6 Oct 2024 01:18:16 -0500
Subject: [PATCH] Update post 02 "Building our Kernel" section

Added an explanation for why the new target still uses Linux conventions
---
 blog/content/edition-2/posts/02-minimal-rust-kernel/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/blog/content/edition-2/posts/02-minimal-rust-kernel/index.md b/blog/content/edition-2/posts/02-minimal-rust-kernel/index.md
index c64f77f1f..fd1d30e3e 100644
--- a/blog/content/edition-2/posts/02-minimal-rust-kernel/index.md
+++ b/blog/content/edition-2/posts/02-minimal-rust-kernel/index.md
@@ -211,7 +211,7 @@ Our target specification file now looks like this:
 ```
 
 ### Building our Kernel
-Compiling for our new target will use Linux conventions (I'm not quite sure why; I assume it's just LLVM's default). This means that we need an entry point named `_start` as described in the [previous post]:
+Compiling for our new target will use Linux conventions, since the ld.lld linker-flavor instructs llvm to compile with the `-flavor gnu` flag (for more linker options, see [the rustc documentation](https://doc.rust-lang.org/rustc/codegen-options/index.html#linker-flavor)). This means that we need an entry point named `_start` as described in the [previous post]:
 
 [previous post]: @/edition-2/posts/01-freestanding-rust-binary/index.md