qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] kqemu+linux-kernel-2.6.25


From: Ben Taylor
Subject: Re: [Qemu-devel] kqemu+linux-kernel-2.6.25
Date: Tue, 13 May 2008 11:49:28 -0400

On Tue, May 13, 2008 at 10:11 AM, ISHWAR RATTAN <address@hidden> wrote:
>
>
>
>  On Mon, 12 May 2008, ISHWAR RATTAN wrote:
>
>
> >
> >
> > On Mon, 12 May 2008, Ben Taylor wrote:
> >
> >
> > >
> > > > Ok after download ./configure end in error as:
> > > >
> > > > ./configure: line 358: unexpected EOF while looking for matching ``'
> > > > ./configure: line 371: syntax error: unexpected end of file
> > > >
> > > > and line 358 given below looks correct to me..
> > > >
> > > >  osrel=`uname -r | nawk -F . '{ printf("%d\n", $1 * 100 + $2); }'`
> > > >
> > >
> > > The problem is in line 34.  the line looks like:
> > >
> > >   cpu="`isainfo | cut -f1 -d\  | sed 's,amd64,x86_64,'"
> > >
> > > but in fact should look like:
> > >
> > >   cpu="`isainfo | cut -f1 -d\  | sed 's,amd64,x86_64,'`"
> > >
> > >
> >
> > Ok. Now configure works but make all results in errori (same error that I
> > see with stock kqemu-1.0.3-pre11:
> > ...
> > make[1]: Leaving directory `/media/sda6/home/ishwar/kqemu/common'
> > make -C /lib/modules/2.6.25-0.slh.11-sidux-686/build M=`pwd` modules
> > make[1]: Entering directory
> `/usr/src/linux-headers-2.6.25-0.slh.11-sidux-686'
> >  CC [M]  /media/sda6/home/ishwar/kqemu/kqemu-linux.o
> > make[2]: *** No rule to make target
> `/media/sda6/home/ishwar/kqemu/kqemu-mod-x86.o', needed by
> `/media/sda6/home/ishwar/kqemu/kqemu-mod.o'.  Stop.
> > make[1]: *** [_module_/media/sda6/home/ishwar/kqemu] Error 2
> > make[1]: Leaving directory
> `/usr/src/linux-headers-2.6.25-0.slh.11-sidux-686'
> > make: *** [kqemu.ko] Error 2
> >
> >
>
>  linux: Linux tigaon 2.6.25-0.slh.11-sidux-686 #1 SMP PREEMPT (form uname
> -a)
>
>  gcc version: gcc version 4.2.3 (Debian 4.2.3-4)
>
>  I just did ./configure and make all in the kqemu-source directory. The
>  error messages are reproduceable.
>
>  -ishwar

Ok.  Let me research a little.

Ben




reply via email to

[Prev in Thread] Current Thread [Next in Thread]