From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Fedora Core 2 Compilation Problems
Date: Wed, 17 Nov 2004 19:03:46 +0100 [thread overview]
Message-ID: <pan.2004.11.17.18.03.45.294226@reply.to> (raw)
In-Reply-To: 50270.64.142.37.183.1100658009.squirrel@64.142.37.183
Le Tue, 16 Nov 2004 18:20:09 -0800, brian a écrit :
> I'm using gcc 3.3.3, binutils 2.15.90.0.3 and glibc 2.3.3. Here are my
> questions:
>
> 1) Is anyone else developing on Fedora Core 2 (or at least with similar
> gcc/binutils/glibc versions) and managing to compile? If so, can you see
> what I am doing wrong?
>
That will not help you to solve your troubles, but I am using
gcc-3.3.4,binutils-2.15,glibc-2.3.3(nptl) and linux-2.6.9 (all vanilla),
qemu compiles and runs perfectly ({i386,ppc}-softmmu are the only one I've
tried ATM).
next prev parent reply other threads:[~2004-11-17 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 2:20 [Qemu-devel] Fedora Core 2 Compilation Problems brian
2004-11-17 18:03 ` Ronald [this message]
2004-11-23 1:34 ` [Qemu-devel] " brian
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=pan.2004.11.17.18.03.45.294226@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--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).