From: Radovan Birdic <radovan.birdic@rt-rk.com>
To: Gary Benson <gbenson@redhat.com>
Cc: infinity@sourceware.org
Subject: Re: Tests fail for big endian architectures
Date: Fri, 28 Apr 2017 09:52:00 -0000 [thread overview]
Message-ID: <886a216e-7532-b120-6043-ed54d9b5e618@rt-rk.com> (raw)
In-Reply-To: <20170426123812.GB18654@blade.nx>
I found an appropriate change that solves the problem.
Thanks a lot!
Regards,
Radovan
On 26.04.2017. 14:38, Gary Benson wrote:
> Hi Radovan,
>
> Radovan Birdic wrote:
>> Package libi8x fails on Debian for all big endian architectures
>> during testing:
>>
>>> make check-TESTS
>>> FAIL: exec/test-deref
>>> FAIL: exec/test-factorial
>>> ========================================
>>> libi8x 0.0.2: tests/test-suite.log
>>> ========================================
> A lot changed since 0.0.2. Does this happen with the latest git?
>
> https://gitlab.com/gbenson/libi8x/
>
> Thanks,
> Gary
>
next prev parent reply other threads:[~2017-04-28 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 11:15 Radovan Birdic
2017-04-26 12:38 ` Gary Benson
2017-04-28 9:52 ` Radovan Birdic [this message]
2017-04-28 13:58 ` Gary Benson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=886a216e-7532-b120-6043-ed54d9b5e618@rt-rk.com \
--to=radovan.birdic@rt-rk.com \
--cc=gbenson@redhat.com \
--cc=infinity@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).