From: Super Bisquit <superbisquit@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question on qemu build environment.
Date: Wed, 27 Apr 2011 12:32:08 -0400 [thread overview]
Message-ID: <BANLkTimoxDoiK5U6Qmh6XcfSWP1_yN8T0g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimzS6dbTgZCHMj2XOviHjV0tMo12Q@mail.gmail.com>
qemu-system-sparc -monitor stdio -vnc :0
With any system emulation, it is the same: high cpu use, no graphical
output, segmentation fault.
On 4/26/11, Super Bisquit <superbisquit@gmail.com> wrote:
> Those are the current settings. I can run ./configure or vi the file to add
> the sparc cpu value. I've installed extra sdl bindings/parts.addons from
> ports.
>
>
> I've enabled gnutls and pcap. Bsd user doesn't work currently for sparc64.
> I had sent the files earlier. These contain patches from nox (Juergen Lock)
> made a patch which helped the port to build.
> I've added WITH_DEBUG=yes to the /etc/make.conf. Something tells me now
> that
> it may be out of context. Probably should be a cflag.
>
> On Tue, Apr 26, 2011 at 2:11 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>
>> On Tue, Apr 26, 2011 at 4:23 PM, Super Bisquit <superbisquit@gmail.com>
>> wrote:
>> > I have noticed that qemu does not fully function on FreeBSD sparc64.
>> > Besides nox@freebsd.org and myself, has anyone tried building and
>> > running qemu under FreeBSD sparc64?
>>
>> I think you are the first to report. On OpenBSD/Sparc64 I could run
>> qemu-system-sparc with the test image and get a command prompt (it
>> seems to be broken now), but i386 emulator (or Sparc64 TCG target) has
>> problems with unaligned accesses.
>>
>
prev parent reply other threads:[~2011-04-27 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 13:23 [Qemu-devel] Question on qemu build environment Super Bisquit
2011-04-26 18:11 ` Blue Swirl
2011-04-27 1:48 ` Super Bisquit
2011-04-27 16:32 ` Super Bisquit [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=BANLkTimoxDoiK5U6Qmh6XcfSWP1_yN8T0g@mail.gmail.com \
--to=superbisquit@gmail.com \
--cc=blauwirbel@gmail.com \
--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).