BRN:Software:Build and Distribution:Linux - Revision history

Jeschke: /* Build */

2006-11-09T14:43:03Z

Build

← Older revision		Revision as of 14:43, 9 November 2006
Line 15:		Line 15:

	= Build =		= Build =
	If your toolchain is installed in different place than "/sde-wgt-toolchain/...", (see [[BRN:Software:Build_and_Distribution:SDE\|SDE]]) please set $CROSS_PATH to your toolchain location:		If your toolchain is installed in different place than "/sde-wgt-toolchain/..." (see [[BRN:Software:Build_and_Distribution:SDE\|SDE]]) -- please set $CROSS_PATH to your toolchain location:
	$ # /sde-wgt-toolchain/... is the default toolchain location (SO YOU DO _NOT_ NEED TO SET $CROSS_PATH!)		$ # /sde-wgt-toolchain/... is the default toolchain location (SO YOU DO _NOT_ NEED TO SET $CROSS_PATH!)
	$ #export CROSS_PATH=/sde-wgt-toolchain/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/		$ #export CROSS_PATH=/sde-wgt-toolchain/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/

2006-11-09T14:42:38Z

Build

← Older revision		Revision as of 14:42, 9 November 2006
Line 15:		Line 15:

	= Build =		= Build =
	If your toolchain is installed in different place than "/sde-wgt-toolchain/...", (see [[BRN:Software:Build_and_Distribution:SDE\|~~Prev~~]]) please set $CROSS_PATH to your toolchain location:		If your toolchain is installed in different place than "/sde-wgt-toolchain/...", (see [[BRN:Software:Build_and_Distribution:SDE\|SDE]]) please set $CROSS_PATH to your toolchain location:
	$ # /sde-wgt-toolchain/... is the default toolchain location (SO YOU DO _NOT_ NEED TO SET $CROSS_PATH!)		$ # /sde-wgt-toolchain/... is the default toolchain location (SO YOU DO _NOT_ NEED TO SET $CROSS_PATH!)
	$ #export CROSS_PATH=/sde-wgt-toolchain/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/		$ #export CROSS_PATH=/sde-wgt-toolchain/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/

2006-11-09T14:42:23Z

Build

← Older revision		Revision as of 14:42, 9 November 2006
Line 15:		Line 15:

	= Build =		= Build =
	If your toolchain is installed in different place than "/sde-wgt-toolchain", please set $CROSS_PATH to your toolchain location:		If your toolchain is installed in different place than "/sde-wgt-toolchain/...", (see [[BRN:Software:Build_and_Distribution:SDE\|Prev]]) please set $CROSS_PATH to your toolchain location:
	$ # /sde-wgt-toolchain is the default toolchain location		$ # /sde-wgt-toolchain/... is the default toolchain location (SO YOU DO _NOT_ NEED TO SET $CROSS_PATH!)
	$ #export CROSS_PATH=/sde-wgt-toolchain		$ #export CROSS_PATH=/sde-wgt-toolchain/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/
	$ sh build.sh # or "sh build.sh -j4" for SMP machines		$ sh build.sh # or "sh build.sh -j4" for SMP machines

2006-11-09T14:38:47Z

Build

← Older revision		Revision as of 14:38, 9 November 2006
Line 15:		Line 15:

	= Build =		= Build =
			If your toolchain is installed in different place than "/sde-wgt-toolchain", please set $CROSS_PATH to your toolchain location:
			$ # /sde-wgt-toolchain is the default toolchain location
			$ #export CROSS_PATH=/sde-wgt-toolchain
	$ sh build.sh # or "sh build.sh -j4" for SMP machines		$ sh build.sh # or "sh build.sh -j4" for SMP machines

2006-11-09T14:31:05Z

Click kernel patch

← Older revision		Revision as of 14:31, 9 November 2006
Line 21:		Line 21:
	$ cd ..		$ cd ..
	$ cvs -d :pserver:anoncvs@cvs.pdos.csail.mit.edu:/cvs co -d click-cvs click/release/one		$ cvs -d :pserver:anoncvs@cvs.pdos.csail.mit.edu:/cvs co -d click-cvs click/release/one
			$ # now obsolete by fixed "linux-2.6.16.13-patch"
	$ svn co $BRN_SVN_REPOS/BerlinRoofNet/trunk/click/patches click-patches		$ #svn co $BRN_SVN_REPOS/BerlinRoofNet/trunk/click/patches click-patches
	$ cd click-cvs		$ #cd click-cvs
	$ patch -p1 -i ../click-patches/click-linux-2.6.16.13-patch.patch # fix some broken stuff
	$ cd ../linux-2.6.16.13		$ #patch -p1 -i ../click-patches/click-linux-2.6.16.13-patch.patch # fix some broken stuff
			$ cd linux-2.6.16.13
	$ patch -p1 -i ../click-cvs/etc/linux-2.6.16.13-patch		$ patch -p1 -i ../click-cvs/etc/linux-2.6.16.13-patch

2006-09-11T10:12:28Z

← Older revision		Revision as of 10:12, 11 September 2006
Line 29:		Line 29:
	If patch was successfully applied, build the modified parts again:		If patch was successfully applied, build the modified parts again:
	$ sh build.sh # or "sh build.sh -j4" for SMP machines		$ sh build.sh # or "sh build.sh -j4" for SMP machines
⚫	$ cd ..

	Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.		Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.

	<span style="color:red">Do not delete your '''System.map''' file! You will need later for building click kernel module.</span>		<span style="color:red">Do not delete your '''System.map''' file! You will need later for building click kernel module.</span>

			= Install Kernel Modules =
			Prepare to create the rootfs of your later used Linux system, by copying linux kernel modules to the "right" location:
			$ make modules_install INSTALL_MOD_PATH=$(pwd)/../root
		⚫	$ cd ..

2006-09-11T10:03:22Z

Click kernel patch

← Older revision		Revision as of 10:03, 11 September 2006
Line 29:		Line 29:
	If patch was successfully applied, build the modified parts again:		If patch was successfully applied, build the modified parts again:
	$ sh build.sh # or "sh build.sh -j4" for SMP machines		$ sh build.sh # or "sh build.sh -j4" for SMP machines
			$ cd ..

	Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.		Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.

2006-09-11T09:57:06Z

Patch

← Older revision		Revision as of 09:57, 11 September 2006
Line 5:		Line 5:

	= Patch =		= Patch =
	$ ~~svn co~~ svn://sarsvn.informatik.hu-berlin.de~~/BerlinRoofNet/trunk/platform/wgt634u/kernel-patches~~		$ BRN_SVN_REPOS=svn://sarsvn.informatik.hu-berlin.de
			$ svn co $BRN_SVN_REPOS/BerlinRoofNet/trunk/platform/wgt634u/kernel-patches
	$ cd linux-2.6.16.13		$ cd linux-2.6.16.13
	$ for p in ../kernel-patches/{generic,mips,brn}/*.patch		$ for p in ../kernel-patches/{generic,mips,brn}/*.patch

2006-09-11T09:49:43Z

Patch

← Older revision		Revision as of 09:49, 11 September 2006
Line 9:		Line 9:
	$ for p in ../kernel-patches/{generic,mips,brn}/*.patch		$ for p in ../kernel-patches/{generic,mips,brn}/*.patch
	> do if [ -r $p ]		> do if [ -r $p ]
	> then patch -p1 -i $p ~~--dry-run~~ \|\| { echo "Apply of patch \"$p\" failed! Exiting..."; break; }		> then patch -p1 -i $p \|\| { echo "Apply of patch \"$p\" failed! Exiting..."; break; }
	> fi		> fi
	> done		> done

2006-09-10T22:34:19Z

Click kernel patch

← Older revision		Revision as of 22:34, 10 September 2006
Line 30:		Line 30:

	Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.		Now you should have a linux kernel (vmlinux), which is able to load the '''click''' router as a linux '''kernel module''', also called ''linuxmodule'' later.

			<span style="color:red">Do not delete your '''System.map''' file! You will need later for building click kernel module.</span>