From: Rakotomandimby Mihamina <mihamina.rakotomandimby@etu.univ-orleans.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu compilation and gcc4 / FC4
Date: Mon, 20 Feb 2006 22:30:02 +0100 [thread overview]
Message-ID: <1140471002.7407.46.camel@localhost.localdomain> (raw)
Hi,
I try to make an FC4 package of qemu 0.8 basing myself on
http://dag.wieers.com/packages/qemu/
FC4 is with gcc4
when just building the src.rpm, I encounter the same problem as this:
http://lists.gnu.org/archive/html/qemu-devel/2005-09/msg00031.html
As I see, there is a "gcc4 patch" in this RPM, but it seems to be not
efficient.
I tried with gcc 4.0.2 and gcc 4.1.0, but it fails.
I also tried to use "compat-gcc-32", but encountered some other errors.
I would like to focus on gcc4.
Has someone found a way to make a FC4 rpm package of qemu 0.8?
--
A powerfull GroupWare, CMS, CRM, ECM: CPS (Open Source & GPL).
Opengroupware, SPIP, Plone, PhpBB, JetSpeed... are good: CPS is better.
http://www.cps-project.org for downloads & documentation.
Free hosting of CPS groupware: http://www.objectis.org.
next reply other threads:[~2006-02-20 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:30 Rakotomandimby Mihamina [this message]
2006-02-21 11:57 ` [Qemu-devel] qemu compilation and gcc4 / FC4 Johannes Schindelin
2006-02-22 23:06 ` Rakotomandimby Mihamina
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=1140471002.7407.46.camel@localhost.localdomain \
--to=mihamina.rakotomandimby@etu.univ-orleans.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).