[Gdal-dev] Error while loading shared libraries: libgdal.1.1.so

[Vincent Schut]

Øystein,

some hints / checks to perform:
- if you do a new compile, usually the best thing is to do this entire set of 
instructions (inside the gdal source dir):
	make distclean (this cleans up all your old object files *and* you old 
configuration options)
	./configure --with-your-options
	check the ouput of ./configure to see whether really all your options were 
included. The mere fact that ./configure did not give any errors is no 
guaranty for this. It might be that GDAL configured OK but leaved out one of 
your options because it could not find something...
	make
	make install (if make ran without errors).
	ldconfig (to tell the dynamic library loader to check the library directories 
for new or changed libraries, like your just compiled libgdal.1.1.so.
This is the usual command sequence for compiling and installing a 
program/library in linux, and sometimes it is too easily assumed that anybody 
knows that...
- is the directory where libgdal.1.1.so is placed (usually /usr/local/lib) in 
the path of the dynamic library? '/usr/local/lib' should either be in the 
file /etc/ld.so.conf, or in the environment variable 'LD_LIBRARY_PATH' (type 
'echo $LD_LIBRARY_PATH'  at the shell command line to check this). If not, 
add it to one of them. Remember that, when you choose to use the environment 
variable, this will be lost after your session. If you want to have it 
persistent, put the line to add it to the variable somewhere in a script that 
is called at each startup/login for the appropriate user. Or use 
/etc/ld.so.conf.
- you can check which dynamically linked libraries a program or other library 
needs by issuing the following command at the shell prompt: ldd 
<programname>. If programname is your program that needs gdal, you will see 
this referenced. This is merely to make sure the error is not somewhere else. 

Probably the first two items of this list will enable you to get things 
working. Oh, and make sure you don't have two versions of the same library at 
two different places, like /usr/lib and /usr/local/lib... But this probably 
won't be the problem in your case, as the linker would find a library then, 
but usually it finds the wrong one...

Regards,
Vincent Schut.
	


On Thursday 27 March 2003 09:01, Øystein Bedin wrote:
> The only build-instructions I found is on this page:
> http://www.remotesensing.org/gdal/gdal_building.html
>
> I couldn't find anything about 'make install' and 'ldconfig' there... So if
> there's something I'm missing here -please tell me.
>
> This is what I did:
> ./configure --with-hdf4=/hdf
> make
>
> I tried to run the make install aftwards - I still get the same error:
> "Error while loading shared libraries: libgdal.1.1.so: cannot open shared
> object file: No such file or directory."
>
> Thanks
> - Øystein
>
>
>
> ----- Original Message -----
> From: "Andrey Kiselev" <dron at ak4719.spb.edu>
> To: <gdal-dev at remotesensing.org>
> Sent: Wednesday, March 26, 2003 11:52 PM
> Subject: Re: [Gdal-dev] Error while loading shared libraries:
> libgdal.1.1.so
>
> > > "Error while loading shared libraries: libgdal.1.1.so: cannot open
> > > shared object file: No such file or directory."
> > >
> > > Seems like the make process is going as it is supposed to - no errors.
> > >
> > > Any suggestions about what the problem might be?
> >
> > Do you complete all building steps, including `make install' and
> > `ldconfig' after all?
> >
> > Regards,
> > Andrey
> >
> > --
> > Andrey V. Kiselev
> > Home phone:  +7 812 5274898  ICQ# 26871517
> > _______________________________________________
> > Gdal-dev mailing list
> > Gdal-dev at remotesensing.org
> > http://remotesensing.org/mailman/listinfo/gdal-dev
>
> _______________________________________________
> Gdal-dev mailing list
> Gdal-dev at remotesensing.org
> http://remotesensing.org/mailman/listinfo/gdal-dev

-- 
______________________________________
Vincent Schut (schut at sarvision.com)
Sarvision B.V.
Wageningen, The Netherlands
www.sarvision.com