mirror of
https://github.com/phil-opp/blog_os.git
synced 2025-12-17 23:07:50 +00:00
Remove sections from URLs
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Cross Compile Binutils"
|
||||
description = ""
|
||||
slug = "cross-compile-binutils"
|
||||
url = "cross-compile-binutils"
|
||||
+++
|
||||
|
||||
The [GNU Binutils] are a collection of various binary tools such as `ld`, `as`, `objdump`, or `readelf`. These tools are platform-specific, so you need to compile them again if your host system and target system are different. In our case, we need `ld` and `objdump` for the x86_64 architecture.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Cross Compiling: libcore"
|
||||
description = ""
|
||||
slug = "cross-compile-libcore"
|
||||
url = "cross-compile-libcore"
|
||||
+++
|
||||
|
||||
If you get an `error: can't find crate for 'core'`, you're probably compiling for a different target (e.g. you're passing the `target` option to `cargo build`). Now the compiler complains that it can't find the `core` library. This document gives a quick overview how to fix this problem. For more details, see the [rust-cross] project.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Catching Exceptions"
|
||||
order = 1
|
||||
slug = "catching-exceptions"
|
||||
url = "catching-exceptions"
|
||||
date = "2016-05-28"
|
||||
updated = "2016-06-25"
|
||||
+++
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Better Exception Messages"
|
||||
order = 2
|
||||
slug = "better-exception-messages"
|
||||
url = "better-exception-messages"
|
||||
date = "2016-08-03"
|
||||
updated = "2016-11-01"
|
||||
+++
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Returning from Exceptions"
|
||||
order = 3
|
||||
slug = "returning-from-exceptions"
|
||||
url = "returning-from-exceptions"
|
||||
date = "2016-09-21"
|
||||
updated = "2016-11-01"
|
||||
+++
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
+++
|
||||
title = "Set Up GDB"
|
||||
description = ""
|
||||
slug = "set-up-gdb"
|
||||
url = "set-up-gdb"
|
||||
+++
|
||||
|
||||
There are a lot of things that can go wrong when developing an OS. So it's a good idea to add a debugger to our toolset, which allows us to set breakpoints and examine variables. We will use [GDB](https://www.gnu.org/software/gdb/) as QEMU supports it out of the box.
|
||||
|
||||
Reference in New Issue
Block a user