src/gnu/usr.bin/ld, branch upstream/2.0_cvs

Tell stupid users to write the bootcode.

1994-11-22T10:58:58+00:00

This commit was manufactured to restore the state of the 2.0-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

This commit was manufactured by cvs2svn to create branch 'ALPHA_2_0'.

1994-11-08T19:51:51+00:00

Add LDDESTDIR to ld command.

1994-09-18T19:41:38+00:00

Add -I${DESTDIR}/usr/include to cpp command.

Unmap hints file when finished with it, so that it can go away

1994-09-15T20:48:55+00:00

completely when ldconfig unlinks it.  If init is shared, then the
referenced unlinked copy of the hints file created by running
ldconfig in /etc/rc caused the file system to be unclean after
every reboot.

Add dependencies on libraries to DPADD. Someday this should be done

1994-08-28T18:49:06+00:00

automagically.  -lfoo has to be right to work, but ${LIBFO0} is too
easy to forget or misspell; nothing checks it and it should be
different for shared libraries.

Install ld.so immutable.

1994-08-26T19:11:14+00:00

Don't explicitly define FreeBSD - this is no longer necessary.

1994-08-19T12:24:45+00:00

Remove reference to the ld.so man page - ain't no such animal.

1994-06-17T17:22:16+00:00

Reported by John Lind.

Changes from Paul Kranenburg which bring us into sync with his sources:

1994-06-15T22:41:19+00:00

 handling of errors through the standard err() and warn()
 more fixes for Geoff Rehmet's NULL pointer bug.
 fixes NULL pointer bugs when linking mono and nested X servers.
 supports a `-nostdlib' option.
 accept object files without a symbol table
 don't attempt dynamic linking when `-A' is given

a few variable names have chaged (desc -> fd), and the formatting has
changed which should make it much easier to track his sources.

I tested 'make world' for /usr/src and X twice with these changes.

Bug reported by Jon-Dean Mountjoy

1994-06-14T12:45:41+00:00

Paul Kranenburg's description:
ld is in error here, assuming that symbols with N_EXT set always have an
entry in the (global) symbol table: this is not the case for C++ generated
constructor/destructor symbols. I can reproduce your failure by fudging
a "multiply defined" constructor symbol by hand. Checking for `g == NULL'
seems to be a ok as a fence for now.

So:
for now, in do_file_warnings() we check if g == NULL, before trying to generate
any warning messages.  This prevents a NULL pointer dereference.