[Liblas-devel] ./configure --with-gdal

Peter Tittmann pwtittmann at ucdavis.edu
Wed Jan 13 21:52:38 EST 2010


Hi,

Two issues I encountered. First attempting to build from the mercurial 
repository:

$ sudo ./autogen.sh
Running aclocal -I m4
./autogen.sh: 30: aclocal: not found

  Something went wrong, giving up!

I'm totally new to mercurial (as well as SVN for that matter), just 
following the INSTALL instructions....


Second issue. I would like to configure the liblas install to work with 
gdal and libgeotiff (to alter spatial reference in the header). Aptitude 
looks like this for gdal:
> $ aptitude search gdal
> p   dans-gdal-scripts                     - GDAL contributed tools by 
> Geographic Informatio
> i A gdal-bin                              - Geospatial Data 
> Abstraction Library - Utility p
> v   gdal-contrib                          
> -                                                
> v   libgdal-dev                           
> -                                                
> i   libgdal-doc                           - Documentation for the 
> Geospatial Data Abstracti
> p   libgdal-perl                          - Perl bindings to the 
> Geospatial Data Abstractio
> p   libgdal-ruby                          - Ruby bindings to the 
> Geospatial Data Abstractio
> p   libgdal-ruby1.8                       - Ruby 1.8 bindings to the 
> Geospatial Data Abstra
> i A libgdal1-1.5.0                        - Geospatial Data 
> Abstraction Library            
> i A libgdal1-1.5.0-grass                  - GRASS extension for the 
> GDAL library           
> i   libgdal1-dev                          - Geospatial Data 
> Abstraction Library - Developme
> i   python-gdal                           - Python bindings to the 
> Geospatial Data Abstract
> v   python2.5-gdal                        
> -                                                
> v   python2.6-gdal                        -  
and like this for libgeotiff:
$ aptitude search libgeotiff
i   libgeotiff-dev                        - the GeoTIFF library -- 
development files      
i   libgeotiff-epsg                       - the GeoTIFF library -- EPSG 
Geodetic Parameter
i   libgeotiff1.2                         - the GeoTIFF library -- 
run-time files  

when i attempt to configure using ./configure i get:
> libLAS configuration summary:
>
>   Version..................: 1.2.1
>   Installation directory...: /usr/local
>   C compiler...............: gcc -Wall -Wno-long-long -pedantic  -O3 
> -DNDEBUG
>   C++ compiler.............: g++ -Wall -Wno-long-long -pedantic 
> -std=c++98  -O3 -DNDEBUG
>   Debugging support........:
>   GDAL support.............: no
>   GeoTIFF SRS support......: no
>
>   LIBS.....................:
>
>   libLAS - http://liblas.org
when I attempt to use the --with-gdal argument i get the following.

$ ./configure --with-gdal
checking build system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
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 g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
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 for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) 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
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared 
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared 
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether byte ordering is bigendian... no
checking for string.h... (cached) yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for debug enabled... no
checking for GDAL... GDAL enabled with gdal-config found in PATH
/usr/bin/gdal-config reports version 1.5.4
checking for libgeotiff... no
configure: error: You must configure a libgeotiff if you are using GDAL 
binaries.  You can configure using a GDAL source tree without 
libgeotiff, but not from binaries.

Any suggestions on either issue will be most gratefully welcomed...

Best regards,

Peter



More information about the Liblas-devel mailing list