[ale] tpdualscan binary - newbie perplexed at compilation error

[Joe Knapka]

OK, this is profoundly weird.

First, does /lib/libc.so.6 exist?

Second, what does "which find" produce?
If not /usr/bin/find, then run ldd on
the result and tell us what you get.

Fer sure, either "which find" != "/usr/bin/find",
or else /lib/libc.so.6 exists, in which case
your link error makes no sense. Sending
us the output of "ls -l /lib/libc.*" might
help.

-- Joe

Jeff Dilcher wrote:
> 
> That gives me:
> 
> libc.so.6 => /lib/libc.so.6 (0x40003000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)
> 
> does that help any?
> 
> > -----Original Message-----
> > From: joe at proxy2.ba.best.com [mailto:joe at proxy2.ba.best.com]On Behalf Of
> > Joe Knapka
> > Sent: Saturday, August 07, 1999 4:21 PM
> > To: Jeff Dilcher
> > Cc: ale at ale.org
> > Subject: Re: [ale] tpdualscan binary - newbie perplexed at compilation
> > error
> >
> >
> > Really, there's no "libc.so*" in /lib? It is rather
> > amazing that anything on your system runs.
> >
> > Just out of curiosity, what happens when you do
> > "ldd /usr/bin/find"?
> >
> > Luck,
> >
> > -- Joe
> >
> > Jeff Dilcher wrote:
> > >
> > > ok, the locate libc.so returned this:
> > >
> > > /usr/i486/-linux-libc5/lib/libc.so.5
> > > /usr/i486/-linux-libc5/lib/libc.so.5.3.12
> > >
> > > So, is that in some type of non standard place, or would
> > > explain why I get the
> > >
> > > ld: cannot open -lc: No such file or directory
> > >
> > > when I compile?  Perhaps there is another library rpm
> > > something or 'nother I need?
> > >
> > > The clueless thank you for your support,
> > >
> > > Jeff
> > >
> > > > -----Original Message-----
> > > > From: owner-ale at ale.org [mailto:owner-ale at ale.org]On Behalf Of
> > > > linuxhat at mailandnews.com
> > > > Sent: Friday, August 06, 1999 6:45 PM
> > > > To: hirsch at mathcs.emory.edu
> > > > Cc: ale
> > > > Subject: RE: [ale] tpdualscan binary - newbie perplexed at compilation
> > > > error
> > > >
> > > >
> > > > On 6 Aug 1999, hirsch at mathcs.emory.edu wrote:
> > > >
> > > > >Try "locate libc.so" to find where your libc is stored.  (For this to work you
> > > > >either have to leave your computer on overnight at least once, or run
> > > > >"/etc/cron.daily/updatedb.cron" once by hand.
> > > >
> > > > or instead of getting complicated, you could use brute force:
> > > >
> > > > find / -name libc.so -print
> > > >
> > > > although I imagine that
> > > >
> > > > find /lib /usr -name libc.so -print
> > > >
> > > > or even
> > > >
> > > > find /lib /usr/lib -name libc.so -print
> > > >
> > > > might be considerably more efficient....
> > > >
> > > > -- Glenn
> > > >
> >
> > -- Joe Knapka
> > * I speak only for myself, except when the little transceiver
> > * at the base of my skull is activated...
> >

-- Joe Knapka
* I speak only for myself, except when the little transceiver
* at the base of my skull is activated...