From: Ishwar Rattan <ishwar@pali.cps.cmich.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-0.8.1 and Solaris-10
Date: Thu, 11 May 2006 15:52:45 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0605111546300.16629@pali.cps.cmich.edu> (raw)
In-Reply-To: <32875489.1146226965470.JavaMail.root@eastrmwml05.mgt.cox.net>
I was able to compile the qemu-cvs code with Taylor's
patches applied. I did not see a qemu executable? Is it
the same as qemu/aprc-softmmu/qemu-system-sparc? When
I try to use it it keeps complaining that it can't
load::
/usr/local/share/qemu/proll.elf: No such file or directory
qemu: could not load prom '/usr/local/share/qemu/proll.bin'
I know I have not installed it in /usr/local as I do not
have the privileges but should this file be somewhere
in the qemu/* (where it was compiled)?
-ishwar
next prev parent reply other threads:[~2006-05-11 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 12:22 [Qemu-devel] PATCH: solaris sparc and hw patch Ben Taylor
2006-05-11 19:52 ` Ishwar Rattan [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 13:20 [Qemu-devel] qemu-0.8.1 and Solaris-10 Ben Taylor
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=Pine.LNX.4.56.0605111546300.16629@pali.cps.cmich.edu \
--to=ishwar@pali.cps.cmich.edu \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).