On Jun 28, 2015, at 11:57 AM, alastair....@gmail.com wrote:Hi,I'm the libdap maintainer in Debian, and have recently been testing the 3.14.0 release which is in Debian unstable now (+ Ubuntu, etc).
It works fine on Intel, amd64, etc. but DMRtest breaks on big-endian architectures: mips, powerpc, sparc, s390x, etc.Is this a known issue?
regardsAlastair McKinstry--
You received this message because you are subscribed to the Google Groups "OPeNDAP Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendap-tech...@opendap.org.
To post to this group, send email to openda...@opendap.org.
Visit this group at http://groups.google.com/a/opendap.org/group/opendap-tech/.
For more options, visit https://groups.google.com/a/opendap.org/d/optout.
On Jun 28, 2015, at 11:57 AM, alastair....@gmail.com wrote:It works fine on Intel, amd64, etc. but DMRtest breaks on big-endian architectures: mips, powerpc, sparc, s390x, etc.Is this a known issue?No, it is not. Any more info you can give would be great.
On Jun 28, 2015, at 11:57 AM, alastair....@gmail.com wrote:It works fine on Intel, amd64, etc. but DMRtest breaks on big-endian architectures: mips, powerpc, sparc, s390x, etc.Is this a known issue?No, it is not. Any more info you can give would be great.
It works fine on Intel, amd64, etc. but DMRtest breaks on big-endian architectures: mips, powerpc, sparc, s390x, etc.Is this a known issue?No, it is not. Any more info you can give would be great.
Att.--Rafael Fonseca
--
You received this message because you are subscribed to the Google Groups "OPeNDAP Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendap-tech...@opendap.org.
To post to this group, send email to openda...@opendap.org.
Visit this group at http://groups.google.com/a/opendap.org/group/opendap-tech/.
For more options, visit https://groups.google.com/a/opendap.org/d/optout.
<DMRTest.log><test-suite.log>
Thanks for the info - I will look into this ASAP, but I’m on travel next week and then out again until 3 Aug.The problem is likely a combination of our switching to ‘reader-makes-right’ meaning the byte-order used for the response is based on the server’s native byte order and either a testing glitch or a bug in the code that computes the received data’s checksum. Thanks very much for finding and reporting this!
Att.--Rafael Fonseca
On November 27, 2015 at 2:38:34 AM, d...@danny.cz (d...@danny.cz) wrote:
On Wednesday, September 23, 2015 at 4:47:05 PM UTC+2, Rafael dos Santos wrote:James,
> > Any update on this? Is there anything I can do to help?
>
> No progress. Yes, I could use access to a machine to test on. Since we’ve
> just finished a big release, now is a good time to look into this.
Sure thing. Can you please fill in this form [1]?
Let me know when you're done and I'll make sure the access is granted asap.
[1] https://fit-rhlab.rhcloud.com/powerlinux-openpower-development-hosting/
Hi,
is there any news about the big endian arches support?
Fixes have been pushed and merged to the master branch.
We no longer need the VM - My apologies if that message never made it back to you.
The issue with big endian support had to do with the checksums - they are dependent on word order. I fixed the tests so they work for each byte order.
James
New URL for the machine access request form is http://research.redhat.com/powerlinux-openpower-development-hosting/
Thanks, Dan