Bug#713644: spatialite-tools: FTBFS: ld: shell.o: undefined reference to symbol 'sqlite3_close'

David Suárez david.sephirot at gmail.com
Sat Jun 22 12:52:08 UTC 2013


Source: spatialite-tools
Version: 3.1.0b-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Maybe you need to add explicitly the offending lib to LD flags.

Relevant part:
> gcc -DHAVE_CONFIG_H -I. -g -O2 -I.    -g -O2 -c shell.c
> /bin/bash ./libtool --tag=CC   --mode=link gcc  -g -O2   -o spatialite shell.o -lspatialite -lfreexl -lm -lreadline  -lproj -lexpat 
> libtool: link: gcc -g -O2 -o spatialite shell.o  -lspatialite -lfreexl -lreadline /usr/lib/libproj.so -lm /usr/lib/x86_64-linux-gnu/libexpat.so
> /usr/bin/ld: shell.o: undefined reference to symbol 'sqlite3_close'
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0: error adding symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/spatialite-tools_3.1.0b-1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Pkg-grass-devel mailing list