From: David Howland <metalliqaz@fastmail.fm>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: port to netbsd
Date: Tue, 31 Aug 2004 19:38:11 -0700 [thread overview]
Message-ID: <41353613.8080304@fastmail.fm> (raw)
In-Reply-To: <87hdqjhqp1.fsf@benpfaff.org>
Ben Pfaff wrote:
> Rename one set of functions or the other. It's probably easier
> to rename qemu's set.
ya, I did that. Just took the hacksaw to it. I similarly hacked up a
few other places. I guess I'll just hack it until it compiles, then
I'll worry about making it clean. Anyway, it gets somewhat further now,
but stops at the following...
---------------------------------------------------------------
/usr/pkg/gcc3/bin/gcc -Wall -O2 -g -fno-strict-aliasing
-fomit-frame-pointe referred-stack-boundary=2 -malign-functions=0
-I. -I/home/dave/build/qemu-0 target-i386
-I/home/dave/build/qemu-0.6.0 -D_GNU_SOURCE -I/home/dave/build/
0.6.0/slirp -c -o op.o /home/dave/build/qemu-0.6.0/target-i386/op.c
cc1: warning: -malign-functions is obsolete, use -falign-functions
../dyngen -o op.h op.o
dyngen: ret or jmp expected at the end of op_divb_AL_T0
gmake[1]: *** [op.h] Error 1
gmake[1]: Leaving directory `/home/dave/build/qemu-0.6.0/i386-softmmu'
---------------------------------------------------------------
This one actually does have me stumped. I don't really see how this is
a NetBSD issue. So...any hints?
thnx,
d
next prev parent reply other threads:[~2004-08-31 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 22:31 [Qemu-devel] port to netbsd (was: FreeBSD != *BSD) David Howland
2004-08-31 22:45 ` [Qemu-devel] Re: port to netbsd Ben Pfaff
2004-09-01 2:38 ` David Howland [this message]
2004-08-31 23:44 ` Paul Brook
2004-09-01 3:27 ` David Howland
2004-08-31 23:57 ` Bochnig, Martin
2004-09-01 3:34 ` David Howland
2004-09-01 14:38 ` Bochnig, Martin
2004-09-01 14:45 ` David Howland
2004-09-01 15:46 ` Richard Zidlicky
2004-08-31 23:58 ` Bochnig, Martin
2004-09-01 5:23 ` [Qemu-devel] " David Howland
2004-09-01 3:25 ` Bochnig, Martin
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=41353613.8080304@fastmail.fm \
--to=metalliqaz@fastmail.fm \
--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).