[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

It's not only for SuperH



For SuperH, I've sorted out the procedure to bootstrap the
distribution (with cross compiling).

It's not only for SuperH.  I believe that you can apply this procedure
to another system, say,  mipsEE.

Here's the procedure,  again:
--------------------------
Prerequisite:
binutils-multiarch
You will need about 10GB disk if you retain all the files.

STEP-0:
Build and install.

STEP-1.0:
Build and install.
Note that gdb is optional.
Only install binutils-sh-linux and binutils-sh-linux-others,
others conflict.

STEP-1.1:
Build and install.
Note that these packages will be replaced in later step.

STEP-1.2:
Build kernel.  Copy kernel-headers.
kernel-headers are used in STEP-1.3.

STEP-1.3:
Build, generate cross package.
Make symbolic link for /usr/sh*-linux/include --> /sur/sh-linux/include.
Install.
Note that you need to setup LINUX_SOURCE environment variable.
Make library link 
	/usr/sh-linux/lib/* --> /usr/sh3-linux/lib/*
	/usr/sh-linux/lib/m4/* --> /usr/sh4-linux/lib/*
	/usr/sh-linux/lib/mb/* --> /usr/sh3eb-linux/lib/*
	/usr/sh-linux/lib/mb/m4/* --> /usr/sh4eb-linux/lib/*

STEP-1.4:
Build.  Remove packages of STEP-1.1, and install.

Only install gcc-slib-sh-linux-others, gcc-slib-sh-linux,
gcc-sh-linux-others, and gcc-sh-linux, others conflict.

STEP-1.5:
Build.  Remove some packages of STEP-1.4 (gcc-slib-sh-linux-others,
gcc-slib-sh-linux), generate cross package and install.
Make library link by /usr/lib/gcc-lib/sh-linux/multilib-symlink


STEP-2.0:
Build, generate cross package and install.
Make library link by /usr/lib/gcc-lib/sh-linux/multilib-symlink

STEP-2.1:
Build, generate cross package and install.
Make library link by /usr/lib/gcc-lib/sh-linux/multilib-symlink

STEP-3.0:
Build.
STEP-3.1:
Build.
STEP-3.2:
Build.
STEP-3.3:
Build.
STEP-3.4:
Build.

STEP-4.0:
Cross install the packages to target system.
Let it boot, login and build and install perl.

STEP-5.0:
On native system, build and install.
-- 



Reply to: