[gdal-dev] RE: gdal1.4 error on RedHat Linux after /usr/loca/lib
upgrade
Gong, Shawn (Contractor)
Shawn.Gong at drdc-rddc.gc.ca
Wed May 7 12:49:32 EDT 2008
hi list,
I built gdal and openev without /usr/local/bin in PATh and that seems
did the trick. Now libgdal.so has no reference to libgeos_c or libgeos
thanks,
Shawn
-----Original Message-----
From: Gong, Shawn (Contractor)
Sent: Wednesday, May 07, 2008 11:09 AM
To: gdal-dev at lists.osgeo.org
Subject: gdal1.4 error on RedHat Linux after /usr/loca/lib upgrade
hi list,
gdal 1.4 and openev 1.8 were build on a RedHat Linux server last Dec and
ran without problem since. gcc 3.2.3 was used to build them.
Recently the gcc was upgraded to 4.0.0 and some libraries were upgraded
as well, namely /usr/local/lib/libcurl, libexpat, libgeos, and libgeos_c
(mainly for gdal 1.5.1 build).
The upgrade makes our (old) gdal 1.4 unworkable: first it complained
that GCC 4.0.0 was not found. After /usr/local/lib was added to the
LD_LIBRARY_PATH, gdal functions generate core dump.
"ldd libgdal.so" revealed that it references to /usr/local/lib/libgeos
/usr/local/lib/libgeos_c (new one using gcc 4) instead of old ones in
[local-installation]/lib, even though [local-installation]/lib is in
LD_LIBRARY_PATH
My questions:
How can I make gdal so that it uses libgeos and other libs in a location
that I desire? So I can include the libs (that I used to make gdal) and
distribute to end-user.
If I can't, then how can I make so the end-user has the right version of
libs under /usr/local/lib, to run gdal.
thanks,
Shawn
More information about the gdal-dev
mailing list