Re: possible minor bug in ld

[Alan Modra]

On Thu, Apr 04, 2002 at 10:51:03PM +0930, Alan Modra wrote:
> On Thu, Apr 04, 2002 at 07:45:38AM -0500, Smith, Ken (G.) wrote:
> > That worked.  Althought I though the manual says that the two versions of 
> > the command are the same.  No?
> 
> No.  The manual hasn't kept pace with the code.

I lie.  The manual has been updated.

"For options whose names are multiple letters, either one dash or two can
precede the option name; for example, @samp{-trace-symbol} and
@samp{--trace-symbol} are equivalent.  Note - there is one exception to
this rule.  Multiple letter options that start with a lower case 'o' can
only be preceeded by two dashes.  This is to reduce confusion with the
@samp{-o} option.  So for example @samp{-omagic} sets the output file
name to @samp{magic} whereas @samp{--omagic} sets the NMAGIC flag on the
output."

This little typo needs fixing though.

        * ld.texinfo (Format Commands <OUTPUT_FORMAT>): Typo fix.

Index: ld/ld.texinfo
===================================================================
RCS file: /cvs/src/src/ld/ld.texinfo,v
retrieving revision 1.66
diff -u -p -r1.66 ld.texinfo
--- ld/ld.texinfo       8 Mar 2002 04:07:21 -0000       1.66
+++ ld/ld.texinfo       8 Apr 2002 00:21:03 -0000
@@ -2277,7 +2277,7 @@ A couple of linker script commands deal 
 @cindex output file format in linker script
 The @code{OUTPUT_FORMAT} command names the BFD format to use for the
 output file (@pxref{BFD}).  Using @code{OUTPUT_FORMAT(@var{bfdname})} is
-exactly like using @samp{-oformat @var{bfdname}} on the command line
+exactly like using @samp{--oformat @var{bfdname}} on the command line
 (@pxref{Options,,Command Line Options}).  If both are used, the command
 line option takes precedence.
 

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre