#3602 closed defect (wontfix)
libproj.so should (perhaps) be libproj.so.0 in ogr/ogrct.cpp
| Reported by: | tbouffon | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OGR_SF | Version: | unspecified |
| Severity: | normal | Keywords: | libproj |
| Cc: |
Description
in ogr/ogrct.cpp, line 84 , LIBNAME is defined as "libproj.so" for unix/linux. But at least rpm-based distros don't ship .so files in base packages, only in devel packages, as the dynamic loader points to versioned libraries. This results in ogr2ogr complaining about the unabilty to load a library whereas it would be possible for ogr2ogr to execute the functions. see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579989 and http://cvs.fedoraproject.org/viewvc/rpms/gdal/F-13/gdal.spec?revision=1.74&view=markup
Change History (2)
comment:1 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
Actually, distros don't ship .so files because the dynamic loader doesn't use it.
Anyway, I'll modify the LIBNAME at build time.
Cheers, Thomas
Note:
See TracTickets
for help on using tickets.
In my opinion, these packages are responsible for setting the LIBNAME when building GDAL to whatever they expect to be available, or alternatively to build, or alternatively to build GDAL with the --with-static-proj4 switch and just make proj.4 a hard dependency of GDAL.
It is hard for me - at the source level - to predict the versioning that might get used in different distributions.