Sender: nate AT cartsys DOT com
Message-ID: <36046AC6.82A0FC99@cartsys.com>
Date: Sat, 19 Sep 1998 19:39:02 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: Ilya Ryzhenkov <orangy AT inetlab DOT com>,
        djgpp workers list <djgpp-workers AT delorie DOT com>
Subject: Re: Exceptions, linker and other ...
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980906124053 DOT 20285R-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

I know this is old, but...

Eli Zaretskii wrote:
> 
> On Sat, 5 Sep 1998, Ilya Ryzhenkov wrote:
> 
> > 3. Is their any tool, which can show the reason of including
> > some .o from libc.a ? I.e. the symbol used, which require other, etc..
> 
> I don't think there is such a tool, but I might be wrong.

I was inspired to write a tool to do this (by parsing `nm' output), got
deep into it, then discovered I was reinventing the wheel.  See the
`--cref' option to `ld'.  With this you can tell what required what to
be included, and you could write something to parse it and report it
prettily.  (A perl script, or some such.)
-- 

Nate Eldredge
nate AT cartsys DOT com