From f4508626804cbcd3ec93a3865f7e2c3ad104c80c Mon Sep 17 00:00:00 2001
From: Tom Tromey <tromey@redhat.com>
Date: Tue, 17 Jul 2001 04:19:40 +0000
Subject: [PATCH] 	* automake.texi (Program and Library Variables):
 Document _LINK.

---
 ChangeLog     |  4 ++++
 automake.texi | 20 ++++++++++++++++----
 stamp-vti     |  2 +-
 version.texi  |  2 +-
 4 files changed, 22 insertions(+), 6 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index d09b5aa4a..e17fa6886 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2001-07-16  Tom Tromey  <tromey@redhat.com>
+
+	* automake.texi (Program and Library Variables): Document _LINK.
+
 2001-07-16  Alexandre Duret-Lutz  <duret_g@epita.fr>
 
 	* automake.in (handle_libraries): Allow libraries to lie in
diff --git a/automake.texi b/automake.texi
index f44f0005d..c96e3e1fe 100644
--- a/automake.texi
+++ b/automake.texi
@@ -1982,6 +1982,19 @@ Use the @samp{_LDFLAGS} variable for this purpose.
 This variable is used to pass extra flags to the link step of a program
 or a shared library.
 
+@item maude_LINK
+You can override the linker on a per-program basis.  By default the
+linker is chosen according to the languages used by the program.  For
+instance, a program that includes C++ source code would use the C++
+compiler to link.  The @samp{_LINK} variable must hold the name of a
+command which can be passed all the @file{.o} file names as arguments.
+Note that the name of the underlying program is @emph{not} passed to
+@samp{_LINK}; typically one uses @samp{$@@}:
+
+@example
+maude_LINK = $(CCLD) -magic -o $@
+@end example
+
 @item maude_CFLAGS
 Automake allows you to set compilation flags on a per-program (or
 per-library) basis.  A single source file can be included in several
@@ -1999,10 +2012,9 @@ object file will be named, for instance, @file{maude-sample.o}.
 
 In compilations with per-program flags, the ordinary @samp{AM_} form of
 the flags variable is @emph{not} automatically included in the
-compilation (however, the user form of the variable @emph{is}
-included).  So for instance, if you want the hypothetical @file{maude}
-compilation to also use the value of @samp{AM_CFLAGS}, you would need to
-write:
+compilation (however, the user form of the variable @emph{is} included).
+So for instance, if you want the hypothetical @file{maude} compilations
+to also use the value of @samp{AM_CFLAGS}, you would need to write:
 
 @example
 maude_CFLAGS = ... your flags ... $(AM_CFLAGS)
diff --git a/stamp-vti b/stamp-vti
index 7f5d863f3..4699f00c2 100644
--- a/stamp-vti
+++ b/stamp-vti
@@ -1,4 +1,4 @@
-@set UPDATED 3 July 2001
+@set UPDATED 16 July 2001
 @set UPDATED-MONTH July 2001
 @set EDITION 1.4i
 @set VERSION 1.4i
diff --git a/version.texi b/version.texi
index 7f5d863f3..4699f00c2 100644
--- a/version.texi
+++ b/version.texi
@@ -1,4 +1,4 @@
-@set UPDATED 3 July 2001
+@set UPDATED 16 July 2001
 @set UPDATED-MONTH July 2001
 @set EDITION 1.4i
 @set VERSION 1.4i
-- 
2.47.2