New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build failure on sparc64 #1508
Comments
A scratch build on s390x passed, so I'm not sure it's big-endian related. |
http://build-failures.rhaalovely.net/sparc64/2019-05-14/devel/proj.log is the full failing log for 6.0, tried 6.1 with similar outcome. |
@landryb I suspect an issue with the sqlite3 binary on this platform. What you can do is modify data/Makefile.am to change the line |
thanks @rouault for the STR, will try over the coming days. Per the logfile, this is using sqlite 3.28.0, as on other platforms where proj builds fine... |
I noticed the same error on my OpenBSD/sparc64 machine and use something similar to produce a /tmp/foo.sql script.
I tried to manually reproduce the problem using the INSERTs in the ellipsoid table. The first line that failed was:
Suspecting a problem with floats, I tweaked "298.2564151" until the INSERT got accepted. So I removed the CHECK constraint on inv_flattening and retried the INSERT without changing the value this time: the INSERT was also accepted. The result:
There's a big nasty bug in sqlite3 on this platform:
Indeed, thank you @rouault for the pointers. |
Please report the bug to the SQLite project. I am closing this since it is not a PROJ issue. |
For the record, https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg115571.html but no feedback (yet?) from upstream. |
And fwiw, ultimately it was a libc bug in OpenBSD, not a bug in sqlite3. Fixed by https://marc.info/?l=openbsd-cvs&m=156113647005489&w=2 |
happens with 6.0 & 6.1 (didnt happen with 5.2), building on OpenBSD/sparc64:
and quite a bunch of others... can provide more details/full log if it helps. I suppose it's related to the endianess somewhere...
The text was updated successfully, but these errors were encountered: