qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: Leonard paniq Ritter <paniq@paniq.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 0.7.2 and gcc 4
Date: Sat, 29 Oct 2005 20:20:28 -0400	[thread overview]
Message-ID: <20051030002028.GA10105@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1130627110.10242.2.camel@zeitgeist>

On Sun, Oct 30, 2005 at 01:05:09AM +0200, Leonard paniq Ritter wrote:
> On Sat, 2005-10-29 at 13:10 -0400, Jim C. Brown wrote:
> > A patch is already available, as noted below.
> 
> but where is it? :)
> 

If you had bothered to search the archives you could have found it yourself.

There is a link to both the gcc 4 patch and to qops here:
http://lilly.csoft.net/~jeffryj/cgi-bin/moin.cgi/FrequentlyAskedQuestions

> > 
> > In any case, most distros allow one to use gcc33 or something to compile
> > programs. I think a 'make CC=gcc33' would do the trick, if you have that
> > compiler installed.
> 
> nope, dont have it installed.

Well all the popular distros have it as a package you can install.

Failing that, there are probably quite a few places that offer precompiled
gcc binaries in tar.gz or tar.bz2 format. I know because I found several.

> is the binary image on
> fabrice.bellard.free.fr qemu enabled?

What binary image?

> 
> > 
> -- 
> -- leonard "paniq" ritter
> -- http://www.mjoo.org
> -- http://www.paniq.org
> 
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2005-10-30  0:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 21:46 [Qemu-devel] qemu 0.7.2 and gcc 4 Leonard "paniq" Ritter
2005-10-26  0:50 ` Jim C. Brown
2005-10-29 15:39   ` Leonard "paniq" Ritter
2005-10-29 17:10     ` Jim C. Brown
2005-10-29 23:05       ` Leonard "paniq" Ritter
2005-10-30  0:20         ` Jim C. Brown [this message]
2005-10-30  1:03           ` Leonard "paniq" Ritter

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=20051030002028.GA10105@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=paniq@paniq.org \
    --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).