Build Xinu - Revision history

AGebhard: /* MIPS */

2024-03-22T00:52:44Z

MIPS

AGebhard at 00:52, 22 March 2024

2024-03-22T00:52:23Z

AGebhard at 00:48, 22 March 2024

2024-03-22T00:48:18Z

AGebhard at 00:45, 22 March 2024

2024-03-22T00:45:57Z

AGebhard at 00:43, 22 March 2024

2024-03-22T00:43:37Z

AGebhard: /* Cross-Compiler */

2024-03-22T00:42:59Z

Cross-Compiler

AGebhard at 00:30, 22 March 2024

2024-03-22T00:30:02Z

Brylow: /* Build GNU C Compiler */

2011-07-12T04:10:46Z

Build GNU C Compiler

Brylow: /* Note about cross-compiler location */

2011-07-12T04:09:12Z

Note about cross-compiler location

Brylow: /* Build binutils */

2011-07-12T04:08:14Z

Build binutils

@@ Line 127: / Line 127: @@
 ----
-=== MIPS ===
+=== MIPS Specific Instructions ===
 Next, you'll want to check your <code> mipsVars </code> file in the <code> compile </code> directory. The file should look something like this:
 <pre>MIPS_ROOT = /usr/local/project/mipsel-dev/bin

@@ Line 19: / Line 19: @@
      sudo yum install autoconf automake python3 libmpc-devel mpfr-devel gmp-devel gawk  bison flex texinfo patchutils gcc gcc-c++ zlib-devel expat-devel
-. Run the configuration script.  By default, it will install the toolchain in `/opt/riscv`.  Change this parameter to install the toolchain in a different location.
+. Run the configuration script.  By default, it will install the toolchain in <code>/opt/riscv</code>.  Change this parameter to install the toolchain in a different location.
      cd riscv-gnu-toolchain && ./configure --prefix=/opt/riscv
@@ Line 27: / Line 27: @@
 . Ensure the directory containing the toolchain is added to the system's PATH.  This is operating system specific.  If the toolchain is not added to the PATH, users will not be able to execute it from any directory.
-. If all has gone well, you should now have a gcc cross-compiler from your host's native architecture to little-endian MIPS:
+. If all has gone well, you should now have a gcc cross-compiler from your host's native architecture to RISC-V 64-bit:
     riscv64-linux-gnu-gcc
@@ Line 96: / Line 96: @@
 == Building the XINU Image ==
-Once you have downloaded and extracted the xinu tarball, you will see a basic directory structure:
+Once you have downloaded and extracted the Xinu tarball, you will see a basic directory structure (depending on the architecture): First, it is a good idea to read up on [[Build System|building the XINU system]].
 <pre>AUTHORS  device   lib      loader   README  system
@@ Line 113: / Line 113: @@
 <tt>LICENSE</tt> is the license under which this project falls.
-<tt>loader/</tt> contains assembly files and is where the bootloader will begin execution of O/S code.
+<tt>loader/</tt> (MIPS only) contains assembly files and is where the bootloader will begin execution of O/S code.
 <tt>mailbox/</tt> contains the source for the mailbox message-passing implementation.
@@ Line 127: / Line 127: @@
 ----
-First, it is a good idea to read up on [[Build System|building the XINU system]]. Next, you'll want to check your <code> mipsVars </code> file in the <code> compile </code> directory. The file should look something like this:
+=== MIPS ===
 <pre>MIPS_ROOT = /usr/local/project/mipsel-dev/bin
 MIPS_PREFIX = mipsel-
@@ Line 167: / Line 168: @@
 == What to do next? ==
-Now that you have successfully built a XINU boot image you're ready to use that file to actually [[HOWTO:Deploy_Xinu|boot XINU]] on your backend router.
+Now that you have successfully built a XINU boot image you're ready to use that file to actually [[HOWTO:Deploy_Xinu|boot XINU]] on your device.
 <hr/>
 ''This work is supported in part by NSF grant DUE-CCLI-0737476.''

← Older revision		Revision as of 00:48, 22 March 2024
Line 26:		Line 26:

	6. Ensure the directory containing the toolchain is added to the system's PATH. This is operating system specific. If the toolchain is not added to the PATH, users will not be able to execute it from any directory.		6. Ensure the directory containing the toolchain is added to the system's PATH. This is operating system specific. If the toolchain is not added to the PATH, users will not be able to execute it from any directory.
		+
		+	7. If all has gone well, you should now have a gcc cross-compiler from your host's native architecture to little-endian MIPS:
		+
		+	riscv64-linux-gnu-gcc

	=== MIPS Cross-Compiler ===		=== MIPS Cross-Compiler ===

@@ Line 22: / Line 22: @@
      cd riscv-gnu-toolchain && ./configure --prefix=/opt/riscv
-. Finally, install the toolchain
+. Install the toolchain
      make linux
 === MIPS Cross-Compiler ===

@@ Line 20: / Line 20: @@
      sudo yum install autoconf automake python3 libmpc-devel mpfr-devel gmp-devel gawk  bison flex texinfo patchutils gcc gcc-c++ zlib-devel expat-devel
 . Run the configuration script.  By default, it will install the toolchain in `/opt/riscv`.  Change this parameter to install the toolchain in a different location.
-     ./configure --prefix=/opt/riscv
+     cd riscv-gnu-toolchain && ./configure --prefix=/opt/riscv
 . Finally, install the toolchain

← Older revision		Revision as of 00:42, 22 March 2024
Line 3:		Line 3:

	== Cross-Compiler ==		== Cross-Compiler ==
		+	=== RISC-V Cross-Compiler and Toolchain ===
		+	The RISC-V cross-compiler and toolchain can be found [[https://github.com/riscv-collab/riscv-gnu-toolchain here]]. Installing the toolchain installs the cross-compiler, LLVM, QEMU, and GCC all with RISC-V support.
		+
		+	==== Installing the Toolchain ====
		+	1. Clone the RISC-V toolchain. Note, this may take a while.
		+
		+	git clone https://github.com/riscv-collab/riscv-gnu-toolchain --recurse-submodules
		+	2. Install the dependencies for your system
		+
		+	'''For Ubuntu'''
		+
		+	sudo apt-get install autoconf automake autotools-dev curl python3 python3-pip libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev ninja-build git cmake libglib2.0-dev
		+
		+	'''For Fedora/CentOS/RHEL OS'''
		+
		+	sudo yum install autoconf automake python3 libmpc-devel mpfr-devel gmp-devel gawk bison flex texinfo patchutils gcc gcc-c++ zlib-devel expat-devel
		+	4. Run the configuration script. By default, it will install the toolchain in `/opt/riscv`. Change this parameter to install the toolchain in a different location.
		+	./configure --prefix=/opt/riscv
		+
		+	5. Finally, install the toolchain
		+	make linux

	=== MIPS Cross-Compiler ===		=== MIPS Cross-Compiler ===

@@ Line 1: / Line 1: @@
 [[Category:HOWTO]]
 The new MIPS port of Embedded XINU has been released.  See the [[Downloads]] tab for more information.
 == Cross-Compiler ==
 In order to compile Embedded MIPS kernels on a workstation that is not itself
 a MIPS processor, it is necessary to build and install an appropriate
@@ Line 16: / Line 17: @@
 lesser-privileged user with write access to the necessary directories.
-=== Build binutils ===
+==== Build binutils ====
 First, we downloaded, compiled, and installed the appropriate binary utilities.
@@ Line 27: / Line 28: @@
     make install
-=== Note about cross-compiler location ===
+==== Note about cross-compiler location ====
 We have chosen the path "/usr/local/project/mipsel-dev" to host our cross-compiler
@@ Line 33: / Line 34: @@
 configuration file, "compile/platforms/*/platformVars" when you arrive at that step.
-=== Link include directory ===
+==== Link include directory ====
 We are not building a true, full-blown UNIX cross-compiler here, and do not need
@@ Line 44: / Line 45: @@
     ln -s /usr/include /usr/local/project/mipsel-dev/mipsel/usr/include
-=== Build GNU C Compiler ===
+==== Build GNU C Compiler ====
 Second, we downloaded, patched, compiled and installed the GNU C Compiler.
@@ Line 57: / Line 58: @@
     make install
-=== Rejoice ===
+==== Rejoice ====
 If all has gone well, you should now have a gcc cross-compiler from your host's native architecture to

@@ Line 47: / Line 47: @@
 Second, we downloaded, patched, compiled and installed the GNU C Compiler.
-We downloaded [http://gcc.gnu.org/ GCC] version 3.4.6.  We applied a
+We downloaded [http://gcc.gnu.org/ GCC] version 4.6.1.  We added the newly compiled binutils
 into the shell path (/usr/local/project/mipsel-dev/bin) for the gcc compilation to find them.
 This is also known to work with [http://gcc.gnu.org/ GCC] version 4.1.2 and 4.2.0 unpatched, using

@@ Line 20: / Line 20: @@
 First, we downloaded, compiled, and installed the appropriate binary utilities.
 We downloaded [http://www.gnu.org/software/binutils/ binutils] version
-[http://ftp.gnu.org/gnu/binutils/binutils-2.18.tar.gz 2.18], untarred the
+[http://ftp.gnu.org/gnu/binutils/binutils-2.21.tar.gz 2.21], untarred the
 source code, and ran the following commands inside the new directory created by untarring the download:
@@ Line 26: / Line 26: @@
     make
     make install
 === Note about cross-compiler location ===