michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 14:27:49 +00:00
Code Issues Projects Releases Wiki Activity

Update post 02 "Building our Kernel" section

Browse Source 
Added an explanation for why the new target still uses Linux conventions
This commit is contained in:
EsotericDryad
2024-10-06 01:18:16 -05:00
committed by GitHub
parent 2b6fc68ad1
commit e0ab3f257d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/content/edition-2/posts/02-minimal-rust-kernel/index.md
View File

@@ -211,7 +211,7 @@ Our target specification file now looks like this:
``` ```
### Building our Kernel ### 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 [previous post]: @/edition-2/posts/01-freestanding-rust-binary/index.md