Re: Re: Starting with beepcore-c

Might be you need to set LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. so it
will pick up the .so from the current directory.

It links against the .so and then should load it at runtime
if it can find it.

-bill


On Fri, Apr 04, 2003 at 12:51:44AM +0200, Sean de Kock wrote:
> On Fri 04 Apr 03 00:45, you wrote:
> > I haven't played around too much with it since the autoconf
> > stuff was completed and the changes to start using libtool.
> >
> > If the profile .so files are not in the examples directory after
> > the build, go find them and copy into the example directory.
> > This should allow the profile to be loaded.
> >
> > -bill
> 
> I found them in threaded_os/examples/unix/.libs. I hav ealready tried to copy 
> them to the examples directory - that did not work. I also tried to copy them 
> straight into /usr/lib but that didn't work either. I saw in the beepd script 
> they relink a bunch of stuff but never any of the profiles, should they have 
> been linked as well - I am not familiar with the way c loads libuaries at 
> runtime? I see in the beepng script the profiles are linked.
> 
> Sean


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/