>Number:         10735
>Category:       misc
>Synopsis:       typo in ld(1) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 01 13:52:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     gabriel rosenkoetter
>Release:        1.5ish
>Organization:
	cs.swarthmore.edu
>Environment:
	
System: NetBSD achemar 1.5_ALPHA NetBSD 1.5_ALPHA (SCINTILA-INSECURE) #0: Mon Jul 31 19:45:12 PDT 2000 gr@cygnus:/usr/src/sys/arch/macppc/compile/SCINTILA-INSECURE macppc


>Description:

In its description of the -e flag, ld(1) says:

       -e entry
               Use entry as the explicit symbol for beginning ex-
              ecution  of  your  program, rather than the default
              entry point.  for a discussion of defaults and oth-
              er ways of specifying the entry point.

I have no idea what belongs at the beginning of the second sentence
there, but something sure does.

>How-To-Repeat:
Try to fix lkm on macppc, find that the call to ld is what's freaking
out, read the ld(1) man page closely. (More on that lkm bit shortly.)
>Fix:
Either don't refer to another source for discussion of entry points,
or find the source. (I'm can't think of a good place off the top of my
head.) Perhaps the ld and binutils info files were intended? Perhaps
objdump(1)? Perhaps Steve Chamberlain's book? Those are all in the
"SEE ALSO" section.
>Release-Note:
>Audit-Trail:
>Unformatted: