Subject: Bug#3782: GNU nm breaks lorder

From: Philip Blundell <[email-masked]>
Date: Mon, 15 Jul 1996 15:52:44 +0100 (BST)

Package: bsdmainutils
Version: 3.1-0

The output generated by GNU nm is slightly incompatible with what lorder 
expects (ie what BSD nm produces).  This means that the output from 
lorder will fail to mention any module that doesn't reference any 
external symbols (and hence, if you're building a library, that module 
may not be added to the library).

I suggest that either the version of lorder that is distributed with 
Debian be changed to take account of GNU nm, or that GNU nm be updated so 
that its output mimics BSD nm more closely.  The former seems like 
a simpler option.

The difference between GNU and BSD nm manifests itself like this:

linux$ nm -go foo.o bar.o
foo.o:00000000 T _some_symbol
bar.o:00000000 T _something_else
linux$

bsd$ nm -go foo.o bar.o

foo.o:
foo.o:00000000 T _some_symbol

bar.o:
bar.o:00000000 T _something_else
bsd$

---

From: Ian Jackson <[email-masked]>
Date: Tue, 16 Jul 96 15:33 BST

Philip Blundell writes ("Bug#3782: GNU nm breaks lorder"):
...
> may not be added to the library).

Could this be related to my problem with libc5_pic, which I posted
recently ?

Ian.

------- start of forwarded message (RFC 934 encapsulation) -------
To: Debian developers list <[email-masked]>
Subject: bootdisks package `generate_library' script and __start___libc_subinit

I tried using this script and produced a library which always gives
the error:
ls: can't resolve symbol '__stop___libc_subinit'
ls: can't resolve symbol '__start___libc_subinit'
(for ls replace whatever binary I'm trying to use).

These symbols are used in set-init.o (inside libc5_pic.a) and never
defined anywhere; the shared /lib/libc.so.5 has it defined somehow.

Fudging this up has only managed to produce a library which makes the
program in question dump core.

I have libc5 and libc5-pic 5.2.18-9, ldso 1.7.14-4 and boot-floppies
1.1.1-9.

Ian.
------- end -------