libspatialite-5.0.1 make check fail

162 views
Skip to first unread message

Konrad J Hambrick

unread,
Aug 16, 2022, 3:14:46 PM8/16/22
to SpatiaLite Users

Sandro --

Thanks for helping with my librasterlite2 issue.

I am now circling back and doing the coverage testing on libspatialite-5.0.1

I failed one test ( check_drop_rename -- see below )

One question I have:  is libspatialite compatible with proj 9.0.1 ?

It seems to cause issues with 
Any other pointers would be welcomed !

Thanks for all your work, Sandro !

-- kjh

This is Slackware64 15.0 

This is my .pc file 

These are the libraries linked 

# ldd /usr/lib64/libspatialite.so.7.1.2
        linux-vdso.so.1 (0x00007ffe69be5000)
        libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007fdf163f0000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdf163cf000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fdf163ca000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fdf16282000)
        libminizip.so.1 => /usr/lib64/libminizip.so.1 (0x00007fdf16275000)
        librttopo.so.1 => /usr/lib64/librttopo.so.1 (0x00007fdf16200000)
        libfreexl.so.1 => /usr/lib64/libfreexl.so.1 (0x00007fdf161f3000)
        libproj.so.25 => /usr/lib64/libproj.so.25 (0x00007fdf15e31000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fdf15e17000)
        libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x00007fdf15cbd000)
        libgeos_c.so.1 => /usr/lib64/libgeos_c.so.1 (0x00007fdf15c75000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fdf15a96000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fdf15a6c000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fdf16d19000)
        libtiff.so.5 => /usr/lib64/libtiff.so.5 (0x00007fdf159e7000)
        libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fdf15943000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fdf1572f000)
        libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fdf15714000)
        libicui18n.so.69 => /usr/lib64/libicui18n.so.69 (0x00007fdf153e2000)
        libicuuc.so.69 => /usr/lib64/libicuuc.so.69 (0x00007fdf151e8000)
        libicudata.so.69 => /usr/lib64/libicudata.so.69 (0x00007fdf1368f000)
        libgeos.so.3.11.0 => /usr/lib64/libgeos.so.3.11.0 (0x00007fdf13403000)
        libwebp.so.7 => /usr/lib64/libwebp.so.7 (0x00007fdf13395000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fdf132d7000)
        libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x00007fdf1322e000)
        libcares.so.2 => /usr/lib64/libcares.so.2 (0x00007fdf13216000)
        libnghttp2.so.14 => /usr/lib64/libnghttp2.so.14 (0x00007fdf131ea000)
        libidn2.so.0 => /usr/lib64/libidn2.so.0 (0x00007fdf131c8000)
        libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007fdf13188000)
        libpsl.so.5 => /usr/lib64/libpsl.so.5 (0x00007fdf13175000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007fdf130dd000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007fdf12df8000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fdf12da6000)
        libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007fdf12d58000)
        liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007fdf12d48000)
        libbrotlidec.so.1 => /usr/lib64/libbrotlidec.so.1 (0x00007fdf12d3b000)
        libunistring.so.2 => /usr/lib64/libunistring.so.2 (0x00007fdf12bb6000)
        libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fdf12adf000)
        libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fdf12ab1000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fdf12aab000)
        libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fdf12a9c000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fdf12a93000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fdf12a79000)
        libnsl.so.2 => /lib64/libnsl.so.2 (0x00007fdf12a5f000)
        libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007fdf12a41000)
        libbrotlicommon.so.1 => /usr/lib64/libbrotlicommon.so.1 (0x00007fdf12a1e000)
        libtirpc.so.3 => /lib64/libtirpc.so.3 (0x00007fdf129ec000



==============================================
   libspatialite 5.0.1: test/test-suite.log
==============================================

# TOTAL: 107
# PASS:  106
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: check_drop_rename
=======================

RenameTable "table_1" error: RenameTable exception - error in trigger ISO_metadata_reference_row_id_value_insert: no such column: rowid.

a.fu...@lqt.it

unread,
Aug 17, 2022, 2:19:31 AM8/17/22
to spatiali...@googlegroups.com
On Tue, 16 Aug 2022 12:14:46 -0700 (PDT), Konrad J Hambrick wrote:
> I failed one test ( check_drop_rename -- see below )
>

this happens because you are using a too much recent version of
libsqlite3

here is the full history: SpatiaLite had a bug that none noticed
(a malformed SQL statement used for automatically creating a
Trigger). Unhappily older versions of libsqlite3 too had a bug
that didn't reported the SQL error, so apparently all was going
well.

at some point a new version of libsqlite3 appeared that finally
detected the SQL error, so now we are left with a (rightfully)
failing test. of course the current development version in
the Fossil repository already contains the fix for this issue.


> One question I have: is libspatialite compatible with proj 9.0.1 ?
>

if I correctly remember there is any recent change releated to proj.

a more comprehensive answer: I'm not really sure if starting a
fresh porting by using the slightly outdated 5.0.1 (released 18
months ago) is the best possible option.

the current development version in the Fossil repository
surely contains several interesting bug fixes applied in
the meanwhile and is surelly well aligned with the more
recent versions of GEOS, PROJ and alike.

if you are possibly interested and do not know Fossil
just try this from the shell:

fossil clone https://www.gaia-gis.it/fossil/libspatialite \
./libspatialite.fossil

mkdir libspatialite

cd libspatialite

fossil open ../libspatialite.fossil

./configure


bye Sandro

Konrad J Hambrick

unread,
Aug 17, 2022, 11:06:35 AM8/17/22
to SpatiaLite Users
Nice one, Sandro.

I'll give it a shot !

Thanks !!

-- kjh

 

Konrad J Hambrick

unread,
Aug 17, 2022, 12:50:11 PM8/17/22
to SpatiaLite Users
Sandro --

Fossil is awesome !

I checked out libspatialite and I also had to update freexl so that configure would complete and now I passed 108 / 108 tests.

Thank you !

-- kjh

 ============================================================================
Testsuite summary for libspatialite 5.1.0-devel
============================================================================
# TOTAL: 108
# PASS:  108

# SKIP:  0
# XFAIL: 0
# FAIL:  0

# XPASS: 0
# ERROR: 0
============================================================================

a.fu...@lqt.it

unread,
Aug 17, 2022, 1:09:44 PM8/17/22
to spatiali...@googlegroups.com
On Wed, 17 Aug 2022 09:50:11 -0700 (PDT), Konrad J Hambrick wrote:
> Fossil is awesome !
>

just for your information

Fossil is developed by Richard Hipp, the father of Sqlite3, and
is the official repository supporting the development of SQLite.

Fossil is fully based on SQLite, so it's elementary simple and
really easy to install, configure and maintain.

just for your information

Fossil is developed by Richard Hipp, the father of Sqlite3, and
is the official repository supporting the development of SQLite.

Fossil is fully based on SQLite, so it's elementary simple and
really easy to install, configure and maintain.

it is certainly not as powerful as the more famous git,
but despite all its simplicity and lightness it can offer
much more than you would expect.

I personally find it perfect for the needs of a not too
complicated project like SpatiaLite, and I'm glad you
appreciated it too.

bye Sandro

Konrad J Hambrick

unread,
Aug 17, 2022, 2:45:15 PM8/17/22
to SpatiaLite Users
Thanks Sandro.

Good Fossil Info !

I have circled back and rebuilt libspatialite and librasterlite2 from fossil clones.

As I mentioned above, to build libspatialite, from the fossil cloned code, I had to update freexl from a fossil clone.

Then to build librasterlite2, I had to install leptonica so that I had liblept.so and /usr/include/leptonica/allheader.h

But the awesome thing about it was, when I built librasterlite2 from 1.1.0-beta1, I originally had 132 warnings about uint16 and uint32 being deprecated

From my build log:

# grep -i warn librasterlite2.SlackBuild-1.1.0-beta1.log |grep uint |sort -k3,3 -k1,1 -u |gawk '{ print $3 }' |uniq -dc
     56 'uint16'
     76 'uint32'

Now, with leptonica installed on my system, the librasterlite2 fossil code builds without any warnings !

Very NICE !

Speaking of dependencies ... are external dependencies for your programs listed anywhere ?

I've looked around but I didn't find them.

Thanks again Sandro !

-- kjh 

Konrad J Hambrick

unread,
Aug 17, 2022, 2:46:33 PM8/17/22
to SpatiaLite Users
p.s. I meant to mention:

 ============================================================================
Testsuite summary for librasterlite2 2.0.0-devel
============================================================================
# TOTAL: 71
# PASS:  71

a.fu...@lqt.it

unread,
Aug 17, 2022, 3:53:28 PM8/17/22
to spatiali...@googlegroups.com
On Wed, 17 Aug 2022 11:45:15 -0700 (PDT), Konrad J Hambrick wrote:
> Speaking of dependencies ... are external dependencies for your
> programs listed anywhere ?
>
> I've looked around but I didn't find them.
>

there is an how-to-guide for building the whole stack on Windows
using MinGW, a porting of gcc adapted to MS platforms:

http://www.gaia-gis.it/gaia-sins/mingw32_how_to.html
http://www.gaia-gis.it/gaia-sins/mingw64_how_to.html

dependencies are always the same as in Linux

bye Sandro

Konrad J Hambrick

unread,
Aug 17, 2022, 4:55:36 PM8/17/22
to spatiali...@googlegroups.com
Thanks Sandro !

Exactly what I was looking for !

-- kjh
Reply all
Reply to author
Forward
0 new messages