[postgis-users] Can't Find liblwgeom for WKT Raster Installation

Jorge Arévalo jorge.arevalo at deimos-space.com
Fri Nov 26 09:21:56 PST 2010


On Fri, Nov 26, 2010 at 5:12 PM, fueldistributa <jeanbouffard at gmail.com> wrote:
>
>
>
> fueldistributa wrote:
>>
>> Hi
>>
>> I'm currently working on setting-up a spatial database on Ubuntu (10.04
>> LTS lycid lynx).  I've installed postgresql 8.4 / postgis 1.5.2 using the
>> synaptic manager command line method in the terminal. I've verified that I
>> have all the necessary requirements, but cannot seem to get pass the
>> ./configure to try and install WKT Raster.
>>
>> This is the following error message that I get, after running the
>> configure line in the wktraster0.1.6d folder;
>> "sudo ./configure
>> --with-postgis-sources=/usr/share/postgresql/8.4/contrib/postgis-1.5"
>>
>> I've pasted the entire ./configure output in case there is something else
>> I'm missing, but the error is at the bottom.
>>
>> error:
>> checking build system type... x86_64-unknown-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking for gcc... gcc
>> checking for C compiler default output file name... a.out
>> checking whether the C compiler works... yes
>> checking whether we are cross compiling... no
>> checking for suffix of executables...
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking for gcc option to accept ANSI C... none needed
>> checking for a sed that does not truncate output... /bin/sed
>> checking for egrep... grep -E
>> checking for ld used by gcc... /usr/bin/ld
>> checking if the linker (/usr/bin/ld) is GNU ld... yes
>> checking for /usr/bin/ld option to reload object files... -r
>> checking for BSD-compatible nm... /usr/bin/nm -B
>> checking whether ln -s works... yes
>> checking how to recognise dependent libraries... pass_all
>> checking how to run the C preprocessor... gcc -E
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking dlfcn.h usability... yes
>> checking dlfcn.h presence... yes
>> checking for dlfcn.h... yes
>> checking for g++... g++
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether g++ accepts -g... yes
>> checking how to run the C++ preprocessor... g++ -E
>> checking for g77... no
>> checking for f77... no
>> checking for xlf... no
>> checking for frt... no
>> checking for pgf77... no
>> checking for fort77... no
>> checking for fl32... no
>> checking for af77... no
>> checking for f90... no
>> checking for xlf90... no
>> checking for pgf90... no
>> checking for epcf90... no
>> checking for f95... f95
>> checking whether we are using the GNU Fortran 77 compiler... yes
>> checking whether f95 accepts -g... yes
>> checking the maximum length of command line arguments... 32768
>> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> checking for objdir... .libs
>> checking for ar... ar
>> checking for ranlib... ranlib
>> checking for strip... strip
>> checking if gcc supports -fno-rtti -fno-exceptions... no
>> checking for gcc option to produce PIC... -fPIC
>> checking if gcc PIC flag -fPIC works... yes
>> checking if gcc static flag -static works... yes
>> checking if gcc supports -c -o file.o... yes
>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
>> shared libraries... yes
>> checking whether -lc should be explicitly linked in... no
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> configure: creating libtool
>> appending configuration tag "CXX" to libtool
>> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
>> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
>> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
>> shared libraries... yes
>> checking for g++ option to produce PIC... -fPIC
>> checking if g++ PIC flag -fPIC works... yes
>> checking if g++ static flag -static works... yes
>> checking if g++ supports -c -o file.o... yes
>> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
>> shared libraries... yes
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> appending configuration tag "F77" to libtool
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> checking for f95 option to produce PIC... -fPIC
>> checking if f95 PIC flag -fPIC works... yes
>> checking if f95 static flag -static works... yes
>> checking if f95 supports -c -o file.o... yes
>> checking whether the f95 linker (/usr/bin/ld -m elf_x86_64) supports
>> shared libraries... yes
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking for gcc... (cached) gcc
>> checking whether we are using the GNU C compiler... (cached) yes
>> checking whether gcc accepts -g... (cached) yes
>> checking for gcc option to accept ANSI C... (cached) none needed
>> checking how to run the C preprocessor... gcc -E
>> checking whether we are using the GNU C++ compiler... (cached) yes
>> checking whether g++ accepts -g... (cached) yes
>> checking if f95 supports -Wall... no
>> checking if f95 supports -Wmissing-prototypes... no
>> checking for flex... flex
>> checking for yywrap in -lfl... yes
>> checking lex output file root... lex.yy
>> checking whether yytext is a pointer... yes
>> checking for bison... bison -y
>> checking for xsltproc... /usr/bin/xsltproc
>> checking for db2pdf... no
>> configure: WARNING: db2pdf is not installed so PDF documentation cannot be
>> built
>> checking for dblatex... no
>> configure: WARNING: dblatex is not installed so PDF documentation cannot
>> be built
>> configure: WARNING: could not locate Docbook stylesheets required to build
>> the documentation
>> checking for low-level RASTER API debug mode... disabled
>> checking for PostGIS RASTER activity debug mode... disabled
>> checking for PostGIS RASTER memory activity debug mode... disabled
>> checking CUnit/CUnit.h usability... no
>> checking CUnit/CUnit.h presence... no
>> checking for CUnit/CUnit.h... no
>> configure: WARNING: could not locate CUnit required for liblwgeom unit
>> tests
>> checking iconv.h usability... yes
>> checking iconv.h presence... yes
>> checking for iconv.h... yes
>> checking for iconv_open in -lc... yes
>> checking for pg_config... /usr/bin/pg_config
>> checking libpq-fe.h usability... yes
>> checking libpq-fe.h presence... yes
>> checking for libpq-fe.h... yes
>> checking for PQserverVersion in -lpq... yes
>> checking for development mode... disabled
>>
>> checking for GDAL... yes
>> checking for GDAL version... 1.7.2
>>
>> configure: error: /usr/share/postgresql/8.4/contrib/postgis-1.5 does not
>> contain liblwgeom/liblwgeom.h or lwgeom/liblwgeom.h, try
>> --with-postgis-sources=DIR (requires postgis svn version)
>>
>> So I've read in a post that liblwgeom was renamed in newer versions of
>> postgis. I'm assuming its the postgis-1.5.so file.
>>
>>
>> How can I get my ./configure to work so I continue with a make & make
>> install?
>> What will I need to do, to get around this liblwgeom issue?
>>
>> I've searched the web with no luck trying to solve this issue, any help
>> would be greatly appreciated.
>>
>> Thank you
>>
>> Jean B.
>>
>
> I've resolved this issue by simply getting the latest SVN snapshot of
> postgis2.0.
>
> Thanks.
>
>
> --
> View this message in context: http://old.nabble.com/Can%27t-Find-liblwgeom-for-WKT-Raster-Installation-tp30308500p30308929.html
> Sent from the PostGIS - User mailing list archive at Nabble.com.
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>

Yes, it is a way to solve it. The problem was because you need the
PostGIS sources in order to compile WKT Raster. With the last version
from SVN, the extension is compiled inside PostGIS.

Best regards,

-- 
Jorge Arévalo
Internet & Mobilty Division, DEIMOS
jorge.arevalo at deimos-space.com
http://mobility.grupodeimos.com/
http://gis4free.wordpress.com



More information about the postgis-users mailing list