wangjiezhe · March 13, 2025 12:58 · Feb 13, 2024 · Oct 8, 2022 · Oct 8, 2022 · Oct 3, 2022
diff --git a/gentoo-crossdev.md b/gentoo-crossdev.md
@@ -34,14 +34,6 @@ Pick a nice looking one, like `default/linux/riscv/20.0/rv64gc/lp64`.
 $ PORTAGE_CONFIGROOT=/usr/riscv64-unknown-linux-gnu eselect profile set default/linux/riscv/20.0/rv64gc/lp64
 ```
 
-## Remove -pam nonsense
-
-Edit `/usr/riscv64-unknown-linux-gnu/etc/portage/make.conf` to remove `USE=-pam` because it'll conflict with `sys-apps/util-linux` being the default `su` provider:
-
-```
-$ sed -i -e "s:-pam::" /usr/riscv64-unknown-linux-gnu/etc/portage/make.conf
-```
-
 ## Avoid circular deps
 
 ```
@@ -70,4 +62,5 @@ See https://wiki.gentoo.org/wiki/Embedded_Handbook/General/Compiling_with_qemu_u
 ## Do it!
 
 1. chroot in to `/usr/riscv64-unknown-linux-gnu` using your preferred method
-2. `emerge -a -uvDU @world` (may need to do `@system` first)
+2. update `/etc/portage/make.conf` to drop ROOT, PORTAGE_TMPDIR, PKG_CONFIG_DIR
+3. `emerge -a -uvDU @world` (may need to do `@system` first)
diff --git a/gentoo-crossdev.md b/gentoo-crossdev.md
@@ -5,7 +5,7 @@ These instructions cover:
 2. populating the new ROOT
 3. making it `chroot`able using qemu-user to easily run "native" builds or tests (this is like a stage3 at the end)
 
-You do not need to follow through to the end.
+You do not need to follow through to the end if you don't need a stage3-like root.
 
 ## Set up the toolchain
 ```

diff --git a/gentoo-crossdev.md b/gentoo-crossdev.md
@@ -3,7 +3,9 @@
 These instructions cover:
 1. building a cross toolchain
 2. populating the new ROOT
-3. making it `chroot`able using qemu-user to easily run "native" builds or tests
+3. making it `chroot`able using qemu-user to easily run "native" builds or tests (this is like a stage3 at the end)
+
+You do not need to follow through to the end.
 
 ## Set up the toolchain
 ```

diff --git a/gistfile1.md → gentoo-crossdev.md b/gistfile1.md → gentoo-crossdev.md
diff --git a/gistfile1.md b/gistfile1.md
@@ -69,6 +69,3 @@ See https://wiki.gentoo.org/wiki/Embedded_Handbook/General/Compiling_with_qemu_u
 
 1. chroot in to `/usr/riscv64-unknown-linux-gnu` using your preferred method
 2. `emerge -a -uvDU @world` (may need to do `@system` first)
-3. `emerge -v1 --with-test-deps --onlydeps sys-libs/glibc`
-4. `FEATURES=test emerge -v1 sys-libs/glibc`
-
diff --git a/gistfile1.md b/gistfile1.md
@@ -1,5 +1,10 @@
 # Cross instructions
 
+These instructions cover:
+1. building a cross toolchain
+2. populating the new ROOT
+3. making it `chroot`able using qemu-user to easily run "native" builds or tests
+
 ## Set up the toolchain
 ```
 $ crossdev riscv64-unknown-linux-gnu

diff --git a/gistfile1.md b/gistfile1.md
@@ -41,3 +41,29 @@ $ sed -i -e "s:-pam::" /usr/riscv64-unknown-linux-gnu/etc/portage/make.conf
 $ USE="-filecaps" riscv64-unknown-linux-gnu-emerge -v1 @system
 ```
 
+# Chroot in
+
+## Set up QEMU
+
+In `/etc/portage/package.use/qemu`, put:
+```
+app-emulation/qemu static-user # optional but makes life easier
+*/* QEMU_USER_TARGETS: riscv32 riscv64
+```
+
+Then `emerge -v app-emulation/qemu`
+
+## binfmt
+
+See https://wiki.gentoo.org/wiki/Embedded_Handbook/General/Compiling_with_qemu_user_chroot.
+
+1. Set up binfmt appropriately for `riscv64` (TODO: explain how, but wiki link above covers it pretty much)
+2. `cp /usr/bin/qemu-riscv64 /usr/riscv64-unknown-linux-gnu/usr/bin/`
+
+## Do it!
+
+1. chroot in to `/usr/riscv64-unknown-linux-gnu` using your preferred method
+2. `emerge -a -uvDU @world` (may need to do `@system` first)
+3. `emerge -v1 --with-test-deps --onlydeps sys-libs/glibc`
+4. `FEATURES=test emerge -v1 sys-libs/glibc`
+
diff --git a/gistfile1.md b/gistfile1.md
@@ -13,6 +13,8 @@ $ riscv64-unknown-linux-gnu-emerge -v1 sys-libs/glibc
 $ riscv64-unknown-linux-gnu-emerge -v1 @system
 ```
 
+There's now already a bunch of things in `/usr/riscv64-unknown-linux-gnu` but we want to make it useful to chroot into and do things.
+
 # Profile setup
 
 

diff --git a/gistfile1.txt → gistfile1.md b/gistfile1.txt → gistfile1.md
diff --git a/gistfile1.txt b/gistfile1.txt
@@ -0,0 +1,41 @@
+# Cross instructions
+
+## Set up the toolchain
+```
+$ crossdev riscv64-unknown-linux-gnu
+```
+
+# Avoid dependency hell and populate the `ROOT`
+Emerge `sys-libs/glibc` (no, `@system` / `@world` won't make it realise it can/should do this, don't ask why, I don't know):
+
+```
+$ riscv64-unknown-linux-gnu-emerge -v1 sys-libs/glibc
+$ riscv64-unknown-linux-gnu-emerge -v1 @system
+```
+
+# Profile setup
+
+
+## Choosing profile
+Run: `PORTAGE_CONFIGROOT=/usr/riscv64-unknown-linux-gnu eselect profile list`
+
+Pick a nice looking one, like `default/linux/riscv/20.0/rv64gc/lp64`.
+
+```
+$ PORTAGE_CONFIGROOT=/usr/riscv64-unknown-linux-gnu eselect profile set default/linux/riscv/20.0/rv64gc/lp64
+```
+
+## Remove -pam nonsense
+
+Edit `/usr/riscv64-unknown-linux-gnu/etc/portage/make.conf` to remove `USE=-pam` because it'll conflict with `sys-apps/util-linux` being the default `su` provider:
+
+```
+$ sed -i -e "s:-pam::" /usr/riscv64-unknown-linux-gnu/etc/portage/make.conf
+```
+
+## Avoid circular deps
+
+```
+$ USE="-filecaps" riscv64-unknown-linux-gnu-emerge -v1 @system
+```
+
No results found