From: Kenn H. <ke...@us...> - 2001-02-03 13:43:32
|
Update of /cvsroot/linux-vax/kernel-2.4/Documentation/vax In directory usw-pr-cvs1:/tmp/cvs-serv20298 Modified Files: README Log Message: Updated to bring it back in sync with reality Index: README =================================================================== RCS file: /cvsroot/linux-vax/kernel-2.4/Documentation/vax/README,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- README 2001/01/18 00:10:39 1.1 +++ README 2001/02/03 13:43:39 1.2 @@ -1,5 +1,5 @@ -Last updated Jul 10, 2000 +Last updated Feb 2, 2000 GETTING STARTED @@ -13,49 +13,24 @@ Unfortunately, there are a few large downloads involved to get up and running... -1. The cross-compiler and binutils - - First download the following: - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/sources/ - - binutils-2.9.1.0.25.tar.bz2 - egcs-1.1.2.tar.bz2 - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/patches/ - - binutils-2.9.1.0.25-20000219.patch.bz2 - egcs-1.1.2-20000219.patch.bz2 - - From ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/ +1. The cross-compiler and binutils - build-vax.sh - one-tree-vax.sh + Grab the sources from CVS: - Create a new directory to unpack all this stuff in and untar the - egcs and binutils tarballs, apply the patches and copy in the shell - scripts: + $ cvs -d:pserver:ano...@cv...:/cvsroot/linux-vax login + (hit return at the password prompt). - $ mkdir vax-cross - $ cd vax-cross - $ tar xvf --use=bzip2 DOWNLOADS/binutils-2.9.1.0.25.tar.bz2 - $ tar xvf --use=bzip2 DOWNLOADS/egcs-1.1.2.tar.bz2 - $ cd binutils-2.9.1.0.25.current - $ patch -p1 < DOWNLOADS/binutils-2.9.1.0.25-20000219.patch - $ cd ../egcs-1.1.2.current - $ patch -p1 < DOWNLOADS/egcs-1.1.2-20000219.patch - $ cd .. - $ cp DOWNLOADS/one-tree-vax.sh DOWNLOADS/build-vax.sh . + $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co tools - Then create the combined binutils/egcs source tree and build it: + Then build the combined binutils/gcc source tree: - $ ./one-tree-vax.sh + $ cd tools $ ./build-vax.sh These should complete without errors. If you get errors, something is seriously wrong and you probably won't get a correctly-installed toolchain. All object files and binaries will be created in - vax-cross/b-vax-dec-linux without touching the source trees. + tools/b-vax-dec-linux without touching the source trees. Then install them: @@ -67,6 +42,9 @@ This will not touch your current GCC installation. + A toolchain snapshot will soon be available for those people who don't + want to compile their own. + 2. The kernel sources Grab the sources from CVS: @@ -75,32 +53,38 @@ (hit return at the password prompt). $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel + + for the tree based on 2.2.14, or + + $ cvs -z9 -d:pserver:ano...@cv...:/cvsroot/linux-vax co kernel-2.4 + + for the 2.4.0 tree. - cd into the kernel dir created by cvs and do + cd into the kernel (or kernel-2.4) dir created by cvs and do $ make oldconfig to create a default .config. (Don't go playing with the config, please. It will probably just break the compile.) - Compile a network-bootable image by doing + Compile a bootable image by doing - $ make mopboot + $ make This will generate plenty of compiler and linker warnings, but you should - end up with a vmlinux.SYS file sized about 280K. + end up with a vmlinux.SYS and a vmlinux.dsk. If you are hacking around in arch/vax, you can do a quicker re-compile by doing - $ make mopbootx + $ make archonly which just rebuilds stuff in arch/vax and re-links the kernel. If you have your VAX and Linux machine on the same SCSI chain and you've got a scratch disk handy, you can do - $ make diskboot && dd if=vmlinux.dsk of=/dev/sdX + $ make && dd if=vmlinux.dsk of=/dev/sdX and then tell your VAX to boot from this disk. This is faster than netbooting. @@ -113,7 +97,7 @@ Sources at - http://www.mssl.ucl.ac.uk/~atp/linux-vax/download/mopd-linux.tar.gz + ftp://linux-vax.sourceforge.net/pub/linux-vax/tools/misc/mopd-linux-vax-2.5.4.tar.gz Compile and install. Create the directory /tftpboot/mop. mopd looks here, and here only, when searching for boot images. @@ -143,6 +127,7 @@ VAXstation 3100/m30 VAXstation 3100/m76 VAXstation 3500 + VAXstation 4000/60 VAXstation II/GPX First you'll want to get your VAX to stop at the >>> console prompt |