Re: [sqlite] endianess/signed issue on OpenBSD/sparc64 ?

On Thu, Jun 13 2019, Richard Hipp wrote: > On 6/9/19, Landry Breuil wrote: >> >> this broke on sparc64 >>>select 298.2564151; >> -298.2564151 >> > > I cannot reproduce this (perhaps because I do not have access to a > sparc64 platform running OpenBSD) and do not have any good ideas about > what

Re: [sqlite] endianess/signed issue on OpenBSD/sparc64 ?

On Thu, Jun 13 2019, Richard Hipp wrote: > On 6/9/19, Landry Breuil wrote: >> >> this broke on sparc64 >>>select 298.2564151; >> -298.2564151 >> > > I cannot reproduce this (perhaps because I do not have access to a > sparc64 platform running OpenBSD) and do not have any good ideas about > what

Re: [sqlite] endianess/signed issue on OpenBSD/sparc64 ?

On 6/9/19, Landry Breuil wrote: > > this broke on sparc64 >>select 298.2564151; > -298.2564151 > I cannot reproduce this (perhaps because I do not have access to a sparc64 platform running OpenBSD) and do not have any good ideas about what might be causing it. If you can get me a temporary

[sqlite] endianess/signed issue on OpenBSD/sparc64 ?

Hi (not subscribed to the list), i'm more or less maintaining sqlite3 in OpenBSD packages (at 3.28.0 now), and recently proj.4 was updated to a version that relies on sqlite3 to store projections, which has some constraints on values entered. this broke on sparc64 (cf