[LV-tools-commit] toolchain/experimental_toolchain README,1.2,1.3

[Jan-Benedict G. <jb...@us...>]

Update of /cvsroot/linux-vax/toolchain/experimental_toolchain
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7076

Modified Files:
	README 
Log Message:
- Document how to do toolchain hacking.


Index: README
===================================================================
RCS file: /cvsroot/linux-vax/toolchain/experimental_toolchain/README,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- README	27 May 2004 15:52:55 -0000	1.2
+++ README	27 May 2004 19:46:27 -0000	1.3
@@ -41,6 +41,29 @@
 this task:)
 
 
+Hacking the Sources
+~~~~~~~~~~~~~~~~~~~
+Basically, you need to check out all the sources once (with --download).
+If you only want to build it, just compile/install from them (with
+--install). However, if you want to help hacking, please follow this
+line:
+
+	$ ./experimental_toolchain.sh --jbglaw --download tempdir installdir
+	$ cd tempdir/source
+	$ mkdir backup-gcc backup-glibc
+	$ (cd gcc-HEAD && tar cf - .;) | (cd backup-gcc && tar xf -;)
+	$ (cd glibc-HEAD && tar cf - .;) | (cd backup-glibc && tar xf -;)
+	$ cd -
+
+After doing a backup of gcc/glibc sources (I think you won't need that
+for binutils, because they work right out of the box), you can hack both
+as you like, build (--install, but no --download) and test it. Later on,
+you can diff out your changes and add the patches to the linux-vax
+CVS project (toolchain/experimental_toolchain/vax-linux-{gcc,glibc}.patch)
+on sf.net, or send them to Jan-Benedict Glaw <jb...@lu...> if you
+don't have CVS write access.
+
+
 Additional Notes
 ~~~~~~~~~~~~~~~~
 Dan Kegel started to investigate in how to do a Canadian Cross. This