Hi Lennart,
On Thu, Jan 23, 2014 at 05:32:44PM +0100, L.C. Karssen wrote:
> Endianness! I should have thought of that. I think the underlying
> library was never developed with endianness in mind. Maybe I can
> convince upstream to fix this. Not sure how useful that would be as I
> don't expect ma
Dear Gert,
The output you pasted in your previous e-mail shows that the checks fail
when comparing output based on ASCII input files with output based on
the binary input files.
On 23-01-14 15:20, Gert Wollny wrote:
> Hello,
>
> I dug around in the code and voila, e.g. in fvlib/frutil.cpp the
>
Dear Paul,
Thanks for the suggestions! I'll see what my sponsor can do.
Best regards,
Lennart.
On 23-01-14 00:27, Paul Wise wrote:
> On Thu, Jan 23, 2014 at 3:59 AM, L.C. Karssen wrote:
>
>> What I can't see is their exact error messages. This is because automake
>> by default runs tests in p
Dear Tobias,
On 23-01-14 07:46, Tobias Frost wrote:
> Another possibility: Use qemu to simulate the target arch... Needs usually a
> good portion of patience, but helped me a couple times already.
>
I'd been thinking about that too. I hoped there was a quicker/easier
solution :-).
Thanks,
L
Hello,
I dug around in the code and voila, e.g. in fvlib/frutil.cpp the
function blockWriteOrRead uses fstream.read|write to do raw data IO and
then in other parts of the code the data is just cast to the desired
type without doing any checks of endianess let alone the needed
conversions.
Now on
Hi,
I have access to a powerpc laptop and took the liberty to run the build.
See the testlog below.
Considering that some of the inputfiles seem to be binary, I would guess
that this problem stems from powerpc (and mips?) being big-endian.
hope that helps,
Gert
===
Another possibility: Use qemu to simulate the target arch... Needs usually a
good portion of patience, but helped me a couple times already.
Paul Wise schrieb:
>On Thu, Jan 23, 2014 at 3:59 AM, L.C. Karssen wrote:
>
>> What I can't see is their exact error messages. This is because
>automake
>>
On Thu, Jan 23, 2014 at 3:59 AM, L.C. Karssen wrote:
> What I can't see is their exact error messages. This is because automake
> by default runs tests in parallel and sends the output of the individual
> tests to a file called test-suite.log. Is there a way to get access to
> that file on the bui
Dear list,
With the help of the Debian-med team I have created the probabel package
for Debian [1]. After uploading I noticed in the buildd logs that the
package fails to build on several architectures (e.g. mips and powerpc).
Looking at the build log [2] I see that the package compiles, but that
9 matches
Mail list logo
