aboutsummaryrefslogtreecommitdiff
path: root/gcc/java
diff options
context:
space:
mode:
Diffstat (limited to 'gcc/java')
-rw-r--r--gcc/java/ChangeLog4
-rw-r--r--gcc/java/gcj.texi14
2 files changed, 18 insertions, 0 deletions
diff --git a/gcc/java/ChangeLog b/gcc/java/ChangeLog
index 49bfd3d..d80ff95 100644
--- a/gcc/java/ChangeLog
+++ b/gcc/java/ChangeLog
@@ -1,3 +1,7 @@
+2006-03-08 David Daney <ddaney@avtrex.com>
+
+ * gcj.texi: Document -static-libgcj option.
+
2006-02-20 Andrew Haley <aph@redhat.com>
* jcf-parse.c (parse_class_file): Set input_location from
diff --git a/gcc/java/gcj.texi b/gcc/java/gcj.texi
index 84e0e16..84659a54 100644
--- a/gcc/java/gcj.texi
+++ b/gcc/java/gcj.texi
@@ -420,6 +420,20 @@ Create an application whose command-line processing is that
of the @code{gij} command.
This option is an alternative to using @code{--main}; you cannot use both.
+
+@item -static-libgcj
+This option causes linking to be done against a static version of the
+libgcj runtime library. This option is only available if
+corresponding linker support exists.
+
+@strong{Caution:} Static linking of libgcj may cause essential parts
+of libgcj to be omitted. Some parts of libgcj use reflection to load
+classes at runtime. Since the linker does not see these references at
+link time, it can omit the referred to classes. The result is usually
+(but not always) a @code{ClassNotFoundException} being thrown at
+runtime. Caution must be used when using this option. For more
+details see:
+@w{@uref{http://gcc.gnu.org/wiki/Statically%20linking%20libgcj}}
@end table
@node Code Generation