[lug] follow up

[Ken Kinder]

Hmm.. I tried linking inside of gcc, which sort of solves my problem
although it's still odd.

Thanks though.

On Wed, Nov 01, 2000 at 04:51:18PM -0700, D. Stimits wrote:
> Ken Kinder wrote:
> > 
> > Ah - I got a reply (Thanks, Ted!) informing me that -lfoo looks for
> > libfoo, so it's not literal. The only problem now is that it's
> > complaining about missing symbals even when the simbals are in
> > libpython1.5.a -- any suggestions?
> > 
> > --
> > Ken Kinder
> > www.kenkinder.com
> > 
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
> Is it at runtime it complains? If so, your libpython1.5.a likely isn't
> in the linker path. Try adding the lib or a sym link to it in your ld
> search path (see /etc/ld.so.conf), then run ldconfig to update the
> contents.
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Ken Kinder
www.kenkinder.com