All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christof Petig <christof@petig-baender.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] powerpc (debian/sid) woes
Date: Tue, 05 Aug 2003 13:18:44 +0200	[thread overview]
Message-ID: <3F2F9294.80800@petig-baender.de> (raw)
In-Reply-To: <1059575253.1749.817.camel@jma1.dev.netgem.com>

Jocelyn Mayer schrieb:
> I compiled a fresh gcc 3.3 tonight.
> I've been able to build all qemu emulator targets,
> after a cvs update with no problems.
> My config is now:
> kernel 2.6.0-test1
> glibc 2.2.5
> gcc 3.3
> binutils 1.13

My problem is not that it does not compile with 3.3 (it actually 
compiles well). If compiled with 3.3 it goes into an endless loop (or 
ill-instructs with -O1). And I can't go back to 2.95 because 2.95 does 
not like the new debian kernel headers.

Anyway the fact that different kernel headers (2.4.21-powerpc) are 
shipped with glibc on debian and used during the compilation might be 
the problem for me.

Perhaps I would have had more luck if I either took my 2.4.21 headers or 
the 2.6.0-test2 headers. I will give it a try (but 2.6.0-test2 does not 
compile for me [problem with event.c])

gcc-3.3        3.3.1-0rc2
binutils       2.14.90.0.5-0.2
libc6-dev      2.3.1-17.0.2 (which ships some kernel headers)
running kernel is  2.4.21-ben2

So my hope was that somebody experienced with ppc on this list might 
spot that the generated assembler code (see my previous mail) was plain 
wrong (or wrongly cut out).
    Christof

  reply	other threads:[~2003-08-05 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 20:09 [Qemu-devel] powerpc (debian/sid) woes Christof Petig
2003-07-29 20:57 ` Fabrice Bellard
2003-07-29 21:33   ` Jocelyn Mayer
2003-07-30 14:27     ` Jocelyn Mayer
2003-08-05 11:18       ` Christof Petig [this message]
2003-08-05 12:26         ` Herbert Pötzl
2003-08-05 13:40         ` Jocelyn Mayer

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=3F2F9294.80800@petig-baender.de \
    --to=christof@petig-baender.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.