From 30621e9b0b52372e0255c983d20bdc8b430494a7 Mon Sep 17 00:00:00 2001 From: Rob Landley Date: Tue, 2 Jan 2024 12:06:35 -0600 Subject: [PATCH] Clean up some version skew in the mkroot instructions. --- www/faq.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/www/faq.html b/www/faq.html index d166bad5..3d5ead48 100755 --- a/www/faq.html +++ b/www/faq.html @@ -17,7 +17,6 @@

  • What is the relationship between toybox and android?

  • Will you backport fixes to old versions?

  • What's this ./ on the front of commands in your examples?

    • -

    Using toybox

    @@ -765,7 +764,7 @@ root/host/fs /init". Type "exit" to get back out.

    Prebuilt binary versions of these system images, suitable for running under the emulator qemu, are uploaded to -the website +the website each release if you'd like to try before building from source.

    You can cross compile simple three package (toybox+libc+linux) systems @@ -776,12 +775,13 @@ and also pointing the build at a Linux kernel source directory, ala:

    make root CROSS=sh4 LINUX=~/linux

    -

    Then you can cd root/sh4; ./qemu-sh4.sh to launch the emulator. -(You'll need the appropriate qemu-system-* emulator binary installed.) -Type "exit" when done and it should shut down the emulator on the way out, -similar to exiting the chroot version. (Except this is more like you ssh'd -to a remote machine: the emulator created its own CPU with its own memory -and I/O devices, and booted a kernel in it.)

    +

    Then you can root/sh4/run-qemu.sh to launch the emulator, +which boots the new Linux system (kernel and root filesystem) on a simulated +CPU with its own memory and I/O devices, connecting the +virtual serial console to the emulator's stdin and stdout. +You'll need the appropriate qemu-system-* emulator binary for the selected +architecture in your $PATH. Type "exit" when done to shut down the emulator, +similar to exiting the chroot version.

    The build finds the three packages needed to produce this system because 1) you're in a toybox source directory, 2) your cross @@ -812,7 +812,7 @@ cd musl-cross-make ln -s $(realpath ccc) ../toybox/ccc -

    If you don't want to do that, you can download prebuilt binary versions +

    If you don't want to do that, you can download prebuilt binary versions and extract them into a "ccc" subdirectory under the toybox source.

    Once you've installed the cross compilers, "make root CROSS=help" @@ -820,7 +820,7 @@ should list all the available cross compilers it recognizes under ccc, something like:

    -aarch64 armv4l armv5l armv7l armv7m armv7r i486 i686 m68k microblaze mips mips64 mipsel powerpc powerpc64 powerpc64le s390x sh2eb sh4 x32 x86_64 +aarch64 armv4l armv5l armv7l armv7m armv7r i486 i686 m68k microblaze mips mips64 mipsel or1k powerpc powerpc64 powerpc64le s390x sh2eb sh4 x32 x86_64

    (A long time ago I @@ -838,7 +838,7 @@ the command line:

    An example package build script (building the dropbear ssh server, adding a port forward from 127.0.0.1:2222 to the qemu command line, and providing a ssh2dropbear.sh convenience script to the output directory) is provided -in the scripts/root directory. If you add your own scripts elsewhere, just +in the mkroot/packages directory. If you add your own scripts elsewhere, just give a path to them on the command line. (No, I'm not merging more package build scripts, I learned that lesson long ago. But if you want to write your own, feel free.)

    -- 2.39.2