On Sat, 19 Jan 2019 20:25:44 +0100, Xavier wrote: > There is a difference earlier between mips and amd64: the first writes: > > # current DEFENSIVE value: 0 > > while the second has "1"
Hm, I don't see "1" in any logs on the buildds and also not in my
local amd64 build log.
> So it seems that these tests should be disabled for mips but it seems
> that SQLITE_DBCONFIG_DEFENSIVE is badly set to a true value.
I'm not sure ... The previous section ('# DEFENSIVE') which queries
SQLITE_DBCONFIG_DEFENSIVE and then turns it on and off, seems to work
fine. Just the last section ('# DEFENSIVE at connection'), where
sqlite_defensive is already set in connect_ok() fails.
Why this set-sqlite_defensive-at-connection-time only fails on mips
is the interesting question …
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Simon And Garfunkel: Sound Of Silence
signature.asc
Description: Digital Signature
