On Fri, 2002-07-26 at 13:35, Steve Witten wrote:

> On Fri, 2002-07-26 at 13:12, William L. Thomson Jr. wrote:
> >
> > You can always put them were you like and place a symlink in the normal
> > place. If the symlink is generic enough, and points to the right thing,
> > it can persist in between releases and version. Or for testing and etc,
> > you can just point it to something else and move on.
> >
> > Just a thought.
>
> Well, yeah... I know that... That's how I discovered this to begin with.
> The problem is that we want to ship FB as part of our solution and we
> don't have any user-callable APIs. By putting the shared libs in
> /usr/lib, kinda makes us have a user-callable API (albeit a pain in the
> butt to discover but nonetheless there ... management droids don't
> understand this -- to them "stuff in /usr/lib == user-callable API").
> It just opens a political can of worms that is not worth the effort to
> battle.

Of course in theory you should be able to modify the /etc/ld.so.conf and
then run ldconfig and be able to put the lib's anywhere but I have yet
to have this work. ldconfig does work and I can see it in the cache, but
when I try to link, most if not all of the time it can't be found. So
not sure if it's something I am doing, or something with the
compiler/linker it self not looking in other places. When it should?

--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone 707.766.9509
Fax 707.766.8989
http://www.obsidian-studios.com