🚀 go-pugleaf

Thomas Conner Annandale uttered...
>   LD_LIBRARY_PATH=/net/hu2/lonely/cs4455/SDL_gfx-2.0.3/local/lib

You need to export the variable, otherwise it will only be local to the
shell.  So, in bash, export LD_LIBRARY_PATH=whatever

-- 
David Shea

> First off, I barely know what I'm talking about, so please bear with me.
> 
> I'm on a Linux box for which I do not have root privileges.  I have
> created a program which uses shared library (?) files which are not in the
> standard paths.  I compile my program with -lSDL_gfx, and I have a
> directory with the files:
> 
>   libSDL_gfx.a 
>   libSDL_gfx.so
>   libSDL_gfx.so.0.0.0
>   libSDL_gfx.la
>   libSDL_gfx.so.0
> 
> When I try to run my program, I get this:
> 
>   ./ServerDriver: error while loading shared libraries: libSDL_gfx.so.0:  
>   cannot open shared object file: No such file or directory
> 
> What do I do to make the executable aware of the directory where it can 
> find the share library?  Remember, I don't have root access.  I read in 
> the 'man ld.so' file that I can set the LD_LIBRARY_PATH environment 
> variable to tell it where to find my libraries, so in bash I typed:
> 
>   LD_LIBRARY_PATH=/net/hu2/lonely/cs4455/SDL_gfx-2.0.3/local/lib
> 
> which is the full directory where the shared library files libSDL_gfx.* 
> files are stored, but it still gives me the same error when I try to run 
> my program.  What do I do?
You can set the LD_LIBRARY_PATH to include the path where the libraries
are nefore running your program. Or you can hardcode the searchpath in the 
binary. e.g. give gcc -Wl,-R /another/path at the linking stage.

-- 
Vennlig hilsen/Best Regards
Nils Olav Sel�sdal
System Engineer
UtelSystems a/s
Tlf: +47 370 45 431
w w w . u t e l s y s t e m s . c o m

> >   LD_LIBRARY_PATH=/net/hu2/lonely/cs4455/SDL_gfx-2.0.3/local/lib
> > 
> > which is the full directory where the shared library files libSDL_gfx.* 
> > files are stored, but it still gives me the same error when I try to run 
> > my program.  What do I do?
> You can set the LD_LIBRARY_PATH to include the path where the libraries
> are nefore running your program. Or you can hardcode the searchpath in the 
> binary. e.g. give gcc -Wl,-R /another/path at the linking stage.

And if both -R switch and LD_LIBRARY_PATH are used, LD_LIBRARY_PATH
will take precedence.

--sony