summaryrefslogtreecommitdiff
path: root/libjava/HACKING
diff options
context:
space:
mode:
authorandreast <andreast@138bc75d-0d04-0410-961f-82ee72b054a4>2004-08-30 18:45:10 +0000
committerandreast <andreast@138bc75d-0d04-0410-961f-82ee72b054a4>2004-08-30 18:45:10 +0000
commita99b42ba10b068fb53518b3bc8ed3c7c4c47eb4a (patch)
treeccec55f42da7f6ac25915554fe72b9f08e58b20b /libjava/HACKING
parentec1e52d19b63afa8bd7aad3fb8bc3c5ef3c9ac02 (diff)
downloadgcc-a99b42ba10b068fb53518b3bc8ed3c7c4c47eb4a.tar.gz
2004-08-30 Andreas Tobler <a.tobler@schweiz.ch>
* HACKING: Remove reference to special automake. No longer needed. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@86793 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libjava/HACKING')
-rw-r--r--libjava/HACKING12
1 files changed, 0 insertions, 12 deletions
diff --git a/libjava/HACKING b/libjava/HACKING
index f0ad859a6ff..a26590596a1 100644
--- a/libjava/HACKING
+++ b/libjava/HACKING
@@ -35,18 +35,6 @@ shared libgcj/classpath file.
If you need to add new java files to libgcj then you have to edit the
Makefile.am file in the top (libjava) directory. And run automake.
-But note the following (thanks to Bryce McKinlay):
-
-> Do you know the magic dance I have to do when adding files to Makefile.am
-> so they will appear in Makefile.in and finally in the user generated
-> Makefile?
-Yup, you need the magic libgcj automake ;-)
-
-<ftp://sources.redhat.com/pub/java/automake-gcj-1.4.tar.gz>
-
-Install that (don't worry, it should still work for other projects), add your
-files to the Makefile.am, then just type "automake" and it will regenerate the
-Makefile.in. Easy!
Tom Tromey adds:
If you add a class to java.lang, java.io, or java.util