From: Rob Landley <rob@landley.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu vs gcc4
Date: Mon, 23 Oct 2006 14:08:23 -0400 [thread overview]
Message-ID: <200610231408.23588.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0610230333380.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On Sunday 22 October 2006 9:45 pm, Johannes Schindelin wrote:
> > I was pondered trying to get tcc to build qemu,
>
> (since tcc only supports x86 targets, this is not really a solution.)
No, it supports arm as well. (And I merged a recent patch to support arm
EABI.) I remember hearing about a PPC patch (although I never tracked that
down), and I was looking into what I needed to do to make it support x86-64.
> > and even made a mercurial copy [...] But Fabrice showed back up on
> > tuesday and checked in a patch, and now I've got a fork that's out of
> > sync with mainline.
>
> I do not really know Mercurial, but it should make it really easy to merge
> two branches (as far as I have been told).
That's the general idea, yes. (In this case what was merged is a reworking of
a patch I already merged, which I could essentially ignore for now.) The
problem is at a higher level: I'd created a fork based of a project that
looked abandoned, but it turned out not to be abandoned, so the fork looks
like a bad idea in retrospect. *shrug* No shortage of other projects to
work on. (Like QEMU: I still haven't managed to install the x86_64 version
of ubuntu. An older version hung when it got to the desktop, in last week's
version I couldn't even get the bios to bring up grub. Need to thump on it
again, but I'm not quite sure how to debug this.)
Rob
--
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery
prev parent reply other threads:[~2006-10-23 18:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:53 [Qemu-devel] qemu vs gcc4 K. Richard Pixley
2006-10-22 22:06 ` Johannes Schindelin
2006-10-23 8:16 ` Martin Guy
2006-10-23 12:20 ` Paul Brook
2006-10-23 13:59 ` Avi Kivity
2006-10-23 14:10 ` Paul Brook
2006-10-23 14:28 ` Avi Kivity
2006-10-23 14:31 ` Paul Brook
2006-10-23 14:35 ` Avi Kivity
2006-10-23 17:41 ` K. Richard Pixley
2006-10-23 17:58 ` Paul Brook
2006-10-23 18:04 ` K. Richard Pixley
2006-10-23 18:20 ` Laurent Desnogues
2006-10-23 18:37 ` Paul Brook
2006-10-24 23:39 ` Rob Landley
2006-10-25 0:24 ` Paul Brook
2006-10-25 19:39 ` Rob Landley
2006-10-26 18:09 ` Daniel Jacobowitz
2006-10-31 16:53 ` Rob Landley
2006-10-31 19:02 ` Paul Brook
2006-10-31 20:41 ` Rob Landley
2006-10-31 22:08 ` Paul Brook
2006-10-31 22:31 ` Laurent Desnogues
2006-10-31 23:00 ` Paul Brook
2006-11-01 0:00 ` Rob Landley
2006-11-01 0:29 ` Paul Brook
2006-11-01 1:51 ` Rob Landley
2006-11-01 3:22 ` Paul Brook
2006-11-01 16:34 ` Rob Landley
2006-11-01 17:01 ` Paul Brook
2006-10-31 23:17 ` Rob Landley
2006-11-01 0:01 ` Paul Brook
2006-10-30 4:35 ` Rob Landley
2006-10-30 14:56 ` Paul Brook
2006-10-30 16:31 ` Rob Landley
2006-10-30 16:50 ` Paul Brook
2006-10-30 22:54 ` Stephen Torri
2006-10-30 23:13 ` Paul Brook
2006-10-23 1:27 ` Rob Landley
2006-10-23 1:44 ` Paul Brook
2006-10-23 1:45 ` Johannes Schindelin
2006-10-23 17:53 ` K. Richard Pixley
2006-10-23 18:08 ` Rob Landley [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=200610231408.23588.rob@landley.net \
--to=rob@landley.net \
--cc=Johannes.Schindelin@gmx.de \
--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).