@vindex AM_GCJFLAGS
+@code{gcj} can be used to compile @file{.java}, @file{.class},
+@file{.zip}, or @file{.jar} files.
+
@node Support for Other Languages, ANSI, Java Support, Programs
@comment node-name, next, previous, up
Although the GNU standards allow the use of ANSI C, this can have the
effect of limiting portability of a package to some older compilers
-(notably SunOS).
+(notably the SunOS C compiler).
Automake allows you to work around this problem on such machines by
@dfn{de-ANSI-fying} each source file before the actual compilation takes
@menu
* Emacs Lisp:: Emacs Lisp
* gettext:: Gettext
-* Guile:: Guile
* Libtool:: Libtool
* Java:: Java
* Python:: Python
nice for everybody else.
-@node gettext, Guile, Emacs Lisp, Other GNU Tools
+@node gettext, Libtool, Emacs Lisp, Other GNU Tools
@section Gettext
@cindex GNU Gettext support
and nothing more.
-@node Guile, Libtool, gettext, Other GNU Tools
-@section Guile
-
-Automake provides some automatic support for writing Guile modules.
-Automake will turn on Guile support if the @code{AM_INIT_GUILE_MODULE}
-macro is used in @file{configure.in}.
-
-Right now Guile support just means that the @code{AM_INIT_GUILE_MODULE}
-macro is understood to mean:
-@itemize @bullet
-@item
-@code{AM_INIT_AUTOMAKE} is run.
-
-@item
-@code{AC_CONFIG_AUX_DIR} is run, with a path of @file{..}.
-@end itemize
-
-As the Guile module code matures, no doubt the Automake support will
-grow as well.
-
-
-@node Libtool, Java, Guile, Other GNU Tools
+@node Libtool, Java, gettext, Other GNU Tools
@section Libtool
Automake provides support for GNU Libtool (@pxref{Top, , Introduction,
@opindex no-installman
@trindex install-man
-Here is how the documentation is handled in GNU @code{cpio} (which
-includes both Texinfo documentation and man pages):
+Here is how the man pages are handled in GNU @code{cpio} (which includes
+both Texinfo documentation and man pages):
@example
-info_TEXINFOS = cpio.texi
man_MANS = cpio.1 mt.1
EXTRA_DIST = $(man_MANS)
@end example
-Texinfo source and info pages are all considered to be source for the
-purposes of making a distribution.
-
Man pages are not currently considered to be source, because it is not
-uncommon for man pages to be automatically generated. For the same
-reason, they are not automatically included in the distribution.
+uncommon for man pages to be automatically generated. Therefore they
+are not automatically included in the distribution. However, this can
+be changed by use of the @samp{dist_} prefix.
+
+The @samp{nobase_} prefix is meaningless for man pages and is
+disallowed.
@node Install, Clean, Documentation, Top