patch to fix nm.c(print_object_filename_bsd) on FreeBSD

[David O'Brien]

On Wed, Apr 19, 2000 at 10:26:48AM -0700, Ian Lance Taylor wrote:
> 
> Hmmm.  I just looked at the NetBSD lorder script, and it looks like
> this:

NetBSD has greatly changed their script then.  It isn't BSD then and
doesn't mean anything.  I dare say the change in NetBSD's script was due
to the wrong output from GNU nm.  The current ``nm'' will not work on
4.3BSD-Tahoe, 4.3BSD-Reno, or true 4.4BSD boxes.

> Michael Sokolov reports that nm -go on BSD4.3 doesn't print the file
> name separately, and I just confirmed that on SunOS as well.

SunOS used a truely achient version of nm (from 4.1c BSD).

> So it sounds like the BSD nm changed behaviour at some point.  I don't
> know when, though.

Please see my next message with dates and CSRG SCCS logs (in RCS format).

> I'm not sure what the best choice is here.  I'm not strongly inclined
> to change the GNU nm behaviour.

Please reconsider.  Either that or please add a new function,
print_object_filename_bsd_anchient() and fix the
print_object_filename_bsd().
 
-- 
-- David    (obrien@NUXI.com)