Symlinks not needed, just adding /usr/local/lib64 so that ldconfig found
the *.so in /usr/local/lib64, which nothing else had used before. The
question however remains, was installing to lib64 a specific choice and
why do neither geos.pc nor geos-config advertise it?
Roger
On Wed, 5 May 2021, Roger Bivand wrote:
Following the decision to drop autotools, I see that cmake generates (in the
current state of the gitea repo) a geos-config that points to /usr/local/lib
for installed shared objects on Linux, but installs in /usr/local/lib64,
leading to other programs not finding them. I know that I can set symlinks,
but geos-config should take the correct values. The geos.pc file is in
/usr/local/lib64/pkgconfig, and reads:
$ cat /usr/local/lib64/pkgconfig/geos.pc
prefix=/usr/local
exec_prefix=${prefix}
includedir=${prefix}/include
libdir=${prefix}/lib
Name: GEOS
Description: Geometry Engine, Open Source - C API
Requires:
Version: 3.10.0dev
Cflags: -I${includedir}
Libs: -L${libdir} -lgeos_c
also pointing at /usr/local/lib, not /usr/local/lib64. Was the instalation
to lib64 a recent change and was it intended?
Best wishes,
Roger
--
Roger Bivand
Emeritus Professor
Department of Economics, Norwegian School of Economics,
Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway.
e-mail: roger.biv...@nhh.no
https://orcid.org/0000-0003-2392-6140
https://scholar.google.no/citations?user=AWeghB0AAAAJ&hl=en
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel
