All of lore.kernel.org
 help / color / mirror / Atom feed
From: G 3 <programmingkidx@gmail.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] Problem with QEMU PPC test image
Date: Thu, 17 Nov 2016 10:50:47 -0500	[thread overview]
Message-ID: <D16631C7-3B87-4FAF-BE3A-89F8CF809DE0@gmail.com> (raw)
In-Reply-To: <20161117154809.GS9606@toto>


On Nov 17, 2016, at 10:48 AM, Edgar E. Iglesias wrote:

> On Thu, Nov 17, 2016 at 10:44:15AM -0500, G 3 wrote:
>>
>> On Nov 17, 2016, at 8:39 AM, Thomas Huth wrote:
>>
>>> On 17.11.2016 03:25, Programmingkid wrote:
>>>> When I run this test disk image: http://wiki.qemu.org/download/ 
>>>> ppc-virtexml507-linux-2_6_34.tgz
>>>>
>>>> I see these error messages:
>>>> /selftest.sh: line 6: /usr/bin/sha1test: not found
>>>> /selftest.sh: line 7: /usr/bin/hmactest: not found
>>>>
>>>> Maybe /usr/bin/sha1sum is what the first test should be. I don't  
>>>> see
>>>> anything that looked like hmactest in the image file.
>>>
>>> I guess these were test programs from the OpenSSL suite:
>>>
>>> https://github.com/openssl/openssl/blob/master/test/sha1test.c
>>> https://github.com/openssl/openssl/blob/master/test/hmactest.c
>>>
>>> ... but apparently have not been included in the image anymore.  
>>> So I'd
>>> suggest that you simply disable them in the selftest.sh script.
>>>
>>> Thomas
>>
>> Thanks for the help.
>
> Hi,
>
> Yes, I think I copied the /selftest.sh script from another rootfs for
> another target that had all the openssl tests.
>
> Cheers,
> Edgar

Could floating point instructions tests be included in the test image?

      reply	other threads:[~2016-11-17 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  2:25 [Qemu-devel] Problem with QEMU PPC test image Programmingkid
2016-11-17 13:39 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2016-11-17 15:44   ` G 3
2016-11-17 15:48     ` Edgar E. Iglesias
2016-11-17 15:50       ` G 3 [this message]

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=D16631C7-3B87-4FAF-BE3A-89F8CF809DE0@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=edgar.iglesias@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.