From ac6e9a31f5b2c19ede9dcabbb861ffcc4dc44c04 Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Sun, 11 Jun 2023 00:13:07 +0800 Subject: [PATCH] loongarch: start branch --- git-version.sh | 2 +- prologue/architecture.xml | 42 +++++++++++++-------------------------- prologue/bookinfo.xml | 2 ++ 3 files changed, 17 insertions(+), 29 deletions(-) diff --git a/git-version.sh b/git-version.sh index 6dd3d90be..396add872 100755 --- a/git-version.sh +++ b/git-version.sh @@ -48,7 +48,7 @@ esac full_date="$month $day$suffix, $year" sha="$(git describe --abbrev=1)" -rev=$(echo "$sha" | sed 's/-g[^-]*$//') +rev=loongarch-$(echo "$sha" | sed 's/-g[^-]*$//') version="$rev" versiond="$rev-systemd" diff --git a/prologue/architecture.xml b/prologue/architecture.xml index d416780e4..b0d87d260 100644 --- a/prologue/architecture.xml +++ b/prologue/architecture.xml @@ -10,41 +10,27 @@ LFS Target Architectures -The primary target architectures of LFS are the AMD/Intel x86 (32-bit) -and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are -also known to work, with some modifications, with the Power PC and ARM CPUs. To -build a system that utilizes one of these alternative CPUs, the main prerequisite, in +The primary target architectures of this LFS edition are LoongArch +CPUs. + +To build a system that utilizes one of these CPUs, the main prerequisite, in addition to those on the next page, is an existing Linux system such as an -earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution -that targets that architecture. (Note that a 32-bit -distribution can be installed and used as a host system on a 64-bit AMD/Intel -computer.) +earlier LFS installation, Loong Arch Linux, CLFS for LoongArch, Gentoo, +Slackware, or other distribution that targets LoongArch. -The gain from building on a 64-bit system, as -compared to a 32-bit system, is minimal. -For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system, -using 4 cores, the following statistics were measured: - -Architecture Build Time Build Size -32-bit 239.9 minutes 3.6 GB -64-bit 233.2 minutes 4.4 GB - -As you can see, on the same hardware, the 64-bit build is only 3% faster -(and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP -server, or a firewall, a 32-bit CPU may be good enough. On the other -hand, several packages in BLFS now need more than 4 GB of RAM to be built -and/or to run; if you plan to use LFS as a desktop, the LFS authors -recommend building a 64-bit system. - -The default 64-bit build that results from LFS is a -pure 64-bit system. That is, it supports 64-bit executables +The build that results from this LFS edition is a +pure lp64d system. That is, it supports executables with +the lp64d ABI only. Building a multi-lib system requires compiling many -applications twice, once for a 32-bit system and once for a 64-bit system. +applications multiple times, once for each ABI to be supported. This is not directly supported in LFS because it would interfere with the educational objective of providing the minimal instructions needed for a basic Linux system. Some of the LFS/BLFS editors maintain a multilib fork of LFS, accessible at . But -that's an advanced topic. +the multilib edition is for x86_64, and multilib is an advanced topic +anyway. diff --git a/prologue/bookinfo.xml b/prologue/bookinfo.xml index 18ba29e02..40aac7b42 100644 --- a/prologue/bookinfo.xml +++ b/prologue/bookinfo.xml @@ -49,6 +49,8 @@ Linux is a registered trademark of Linus Torvalds. + LoongArch is a + registered trademark of Loongson Technology Co., Ltd.