Quote:
Originally Posted by knudfl
Postgis 1.4.0 : No problems, when /usr/local/lib/
is in the LD_LIBRARY_PATH. In CentOS4 : no.
Suggest : export LD_LIBRARY_PATH=/usr/local/lib/
or add /usr/local/lib/ to /etc/ld.so.conf
.. or ..
# yum search geos geos-devel
.. the epel repo has version 2.2.3
.. rpmforge.repo : 3.1.0
.. or : cd geos-3.1.1/
# make uninstall && exit
./configure --prefix=/usr/
.....
|
Well I eventually managed to successfully compile postgis by using
LDFLAGS=-lstdc++ ./configure. A helpful poster in postgis mailing list told me so, and I just followed his instruction. And everything compiled fine.
Yet I don't really have an idea what does it mean. Someone at TechReport said that LDFLAGS is forcing the linker to search the Standard C++ library in addition to any other libraries, but that's all he said. (sorry, I'm a noob)
(1) Is libgeos_c a standard C++ library? Probably it explains why ./configure failed to find the file, despite I have ran ldconfig ad nauseam.
(2) What is the drawback of using Standard C++ library? (LDFLAGS=-lstdc++)
(3) Is there any problem I have to anticipate in the future? I mean, during runtime?
(4) I will compile MapServer next week, which, by the way, need geos-3.1.1 as well. I have to specify --with-geosconfig=/usr/local/bin/geos-config again in ./configure. Will this problem persists? Should I use
LDFLAGS=-lstdc++ ./configure again? Should I use LD_LIBRARY_PATH? But I read in Google that using LD_LIBRARY_PATH is asking for trouble, is that true?
[5](5)[/b]
Quote:
Originally Posted by knudfl
Suggest : export LD_LIBRARY_PATH=/usr/local/lib/
or add /usr/local/lib/ to /etc/ld.so.conf
|
]
I have added /usr/local/lib to /etc/ld.so.conf, and I have run ldconfig many times. Why did it fail?