Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!news.kei.com!ub!galileo.cc.rochester.edu!newstand.syr.edu!rodan.syr.edu!smcarey From: smcarey@rodan.syr.edu (Shawn M Carey) Subject: Re: Libraries and X emulation Message-ID: <1994Jun11.132851.21090@newstand.syr.edu> Sender: netnews@newstand.syr.edu (Network News Administrator) Nntp-Posting-Host: rodan.syr.edu Organization: Syracuse University, Syracuse, NY References: <Cr52A4.6x7@world.std.com> <DFR.94Jun10131655@minnow.render.com> Date: Sat, 11 Jun 1994 13:28:51 GMT Lines: 22 In article <DFR.94Jun10131655@minnow.render.com> dfr@render.com (Doug Rabson) writes: >In article <Cr52A4.6x7@world.std.com> mcgovern@world.std.com (Brian J McGovern) writes: > >> Two quick questions.... >> 1.) Is there a utility for looking at the standard libraries in /usr/lib, and >> deriving which functions are in which. Only being a semi-qualified Unix >> programmer, I often have the problem of linking random libraries (with best >> guesses) looking for a specific function call. If I could create a dynamic >> list that I can "grep", it'd be perfect... > >Try "nm /usr/lib/*.a" > This doesn't show you which library the symbol was found in. I've used something like this in the past: foreach lib ( /usr/lib/*.a ) ? echo searching $lib ? nm -g $lib | grep function_name ? end -Shawn Carey