qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jocelyn Mayer <jma@netgem.com>
To: qemu mailing list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] powerpc (debian/sid) woes
Date: 05 Aug 2003 15:40:40 +0200	[thread overview]
Message-ID: <1060090840.1749.6595.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <3F2F9294.80800@petig-baender.de>

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Tue, 2003-08-05 at 13:18, Christof Petig wrote:
> 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.
> 
I need to do more tests to check if this ever happens for me...

> 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])
Here's the patch you need to make it compile:



[-- Attachment #2: evdev.c.diff --]
[-- Type: text/plain, Size: 735 bytes --]

--- evdev.c.old	Mon Jun 16 06:39:02 2003
+++ evdev.c	Thu Jul 31 02:41:35 2003
@@ -208,7 +208,7 @@
 	struct evdev *evdev = list->evdev;
 	struct input_dev *dev = evdev->handle.dev;
 	struct input_absinfo abs;
-	int i, t, u;
+	int i, t, u, v;
 
 	if (!evdev->exist) return -ENODEV;
 
@@ -240,7 +240,8 @@
 			if (get_user(t, ((int *) arg) + 0)) return -EFAULT;
 			if (t < 0 || t > dev->keycodemax || !dev->keycodesize) return -EINVAL;
 			u = INPUT_KEYCODE(dev, t);
-			if (get_user(INPUT_KEYCODE(dev, t), ((int *) arg) + 1)) return -EFAULT;
+                        v = INPUT_KEYCODE(dev, t);
+			if (get_user(v, ((int *) arg) + 1)) return -EFAULT;
 
 			for (i = 0; i < dev->keycodemax; i++)
 				if(INPUT_KEYCODE(dev, t) == u) break;

      parent reply	other threads:[~2003-08-05 13:40 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
2003-08-05 12:26         ` Herbert Pötzl
2003-08-05 13:40         ` Jocelyn Mayer [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=1060090840.1749.6595.camel@jma1.dev.netgem.com \
    --to=jma@netgem.com \
    --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).