From: Jeffrey Osier <jeffrey@cygnus>
Date: Tue, 29 Mar 1994 00:53:16 +0000 (+0000)
Subject: 	binutils.texi(nlmconv): added -d/--debug and -l/--linker info
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=20465f8bd11990cf71205be5f44aed9c303f52b5;p=binutils-gdb.git

	binutils.texi(nlmconv): added -d/--debug and -l/--linker info
---

diff --git a/binutils/binutils.texi b/binutils/binutils.texi
index 215a6e4c8d1..4b78ed796f5 100644
--- a/binutils/binutils.texi
+++ b/binutils/binutils.texi
@@ -1348,6 +1348,7 @@ utilities, since it is only useful for NLM targets.
 nlmconv [ -I @var{bfdname} | --input-target=@var{bfdname} ]
         [ -O @var{bfdname} | --output-target=@var{bfdname} ]
         [ -T @var{headerfile} | --header-file=@var{headerfile} ]
+        [ -d | --debug]  [ -l @var{linker} | --linker=@var{linker} ]
         [ -h | --help ]  [ -V | --version ]
         @var{infile} @var{outfile}
 @end smallexample
@@ -1363,6 +1364,11 @@ Developer's Kit (``NLM SDK''), available from Novell, Inc.
 @var{infile}; see @ref{BFD,,BFD,ld.info,Using LD}, for
 more information.
 
+@code{nlmconv} can perform a link step.  In other words, you can list
+more than one object file for input if you list them in the definitions
+file (rather than simply specifying one input file on the command line).
+In this case, @code{nlmconv} calls the linker for you.
+
 @table @code
 @item -I @var{bfdname}
 @itemx --input-target=@var{bfdname}
@@ -1385,6 +1391,15 @@ writing the NLM command file language used in header files, see@ see the
 Overview}, which is part of the NLM Software Developer's Kit, available
 from Novell, Inc.
 
+@item -d
+@itemx --debug
+Displays (on standard error) the linker command line used by @code{nlmconv}.
+
+@item -l @var{linker}
+@itemx --linker=@var{linker}
+Use @var{linker} for any linking.  @var{linker} can be an abosolute or a
+relative pathname.
+
 @item -h
 @itemx --help
 Prints a usage summary.