From: "Marcello 'R.D.O.' Magnifico" <marcello.magnifico@e-cremona.it>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] compiling fails, at least one little thing to fix in sources
Date: Sat, 14 Aug 2004 23:36:01 +0200 [thread overview]
Message-ID: <20040814233601.C1935@aquarius> (raw)
Hi all,
I'm trying to compile 0.6.0 official sources from the main
site, on a Red Hat 7.3, having seen in the docs that it should have the
right tools for the job. GCC complains very shortly about a couple of
const and char definitions in vmdk2raw.c and the making stops. Moving
definitions up to the beginning of the functions they belong to, seems
solving. Have already seen that with sources from different projects,
this might be a GCC backport issue, but I remember having seen that on
a RH7.2, too. Anyway, I believe this bug should be fixed in the
official sources.
But, after that, there is another blocking trouble:
cpu-exec.c:528: more than 10 operands in `asm'.
Anyone has the clue? for this time I don't. Maybe this might open the
road to get an even more portable official code, dunno. Too bad I'm no
real C programmer, just poking around for fun.
yo,
RDO
reply other threads:[~2004-08-14 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040814233601.C1935@aquarius \
--to=marcello.magnifico@e-cremona.it \
--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).