Scott <[email protected]> writes: > Postgis configure is robust and allows you to set/unset all sorts of > things, including rpath. Mine looks like: > > ./configure \ > --prefix=/export/gis/local \ > --with-gdalconfig=/export/path/bin/gdal-config \ > --with-geosconfig=/export/path/bin/geos-config \ > --with-pgconfig=/usr/lib/postgresql/15/bin/pg_config \ > --with-sfcgal=/export/path/bin/sfcgal-config
I'm assuming /export/path is the prefix for which you compiled those 4, and you are trying to put postgis under /export/gis. > The problem is the environment. When I do an ldd on the newly built > postgis-3.so, all the paths are correct *if* in my user environment. > From another user, the paths default to the system pkg path where the > older geos 3.11 version is installed. That's a clue that there is LD_LIBRARY_PATH set somehow. See my first message about objdump. Unfortunately I think the only way to get through this is to understand how dynamic linking is working. (Of course, you may find that Debian says that RPATH is bad and LD_LIBRARY_PATH is the right thing to do. I'm really unclear on their doctrine, and I hope my impressions are confused.) You should also save the build logs, and look at the rpath arguments on the link lines. You probably have to set CMAKE_VERBOSE or some such, because people these days seem to think that hiding actual build commands is a good thing.
