-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
1.11.0 test failure on big endian architectures #176
Comments
Looks like the "Spaten" export depends on byte-order. Not hugely important, but we have to look into this. |
Yes, the docs state:
Converting the data to LE should resolve the issue, I think. |
The problem as you say is that So I guess we need to have two sets of valid output or something and allow either, or the correct one for the current host... |
There are several issues here:
|
Thanks everyone for the analysis. At the moment I would tend to restrict WKB to little endian in the specification, which would simplify decoder implementation. As a reference point: PostGIS defaults to server byte order, but is able export either.
True, the tests are very primitive, but I am not sure how to test output without a dedicated decoder. Do you have a suggestion how to solve this, @joto? |
The issue is still present in 1.11.1: |
Remove the |
Seeing the same test failures on s390x for the Debian package:
|
The Debian package build for 1.11.0 failed on s390x due to test failures:
Full buildlogs: s390x
hexdump diffs:
The text was updated successfully, but these errors were encountered: