kvm-userspace fails to compile

kvm-userspace fails to compile

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

The error is:

libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_access_report':
/home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:221:
undefined reference to `kvm_enable_vapic'
libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup':
/home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:287:
undefined reference to `kvm_enable_tpr_access_reporting'
collect2: ld returned 1 exit status
make[2]: *** [qemu-system-x86_64] Error 1
make[2]: Leaving directory
`/home/vivierl/Projects/KVM/kvm-userspace/qemu/x86_64-softmmu'
make[1]: *** [subdir-x86_64-softmmu] Error 2
make[1]: Leaving directory
`/home/vivierl/Projects/KVM/kvm-userspace/qemu'
make: *** [qemu] Error 2

Any idea ?

Laurent
-- 
----------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

kvm-userspace fails to compile

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

The error is:

libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_access_report':
/home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:221:
undefined reference to `kvm_enable_vapic'
libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup':
/home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:287:
undefined reference to `kvm_enable_tpr_access_reporting'
collect2: ld returned 1 exit status
make[2]: *** [qemu-system-x86_64] Error 1
make[2]: Leaving directory
`/home/vivierl/Projects/KVM/kvm-userspace/qemu/x86_64-softmmu'
make[1]: *** [subdir-x86_64-softmmu] Error 2
make[1]: Leaving directory
`/home/vivierl/Projects/KVM/kvm-userspace/qemu'
make: *** [qemu] Error 2

Any idea ?

Laurent
-- 
----------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-userspace fails to compile

[Dor Laor]

On Mon, 2008-01-07 at 14:14 +0100, Laurent Vivier wrote:
> The error is:
> 
> libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_access_report':
> /home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:221:
> undefined reference to `kvm_enable_vapic'
> libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup':
> /home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:287:
> undefined reference to `kvm_enable_tpr_access_reporting'
> collect2: ld returned 1 exit status
> make[2]: *** [qemu-system-x86_64] Error 1
> make[2]: Leaving directory
> `/home/vivierl/Projects/KVM/kvm-userspace/qemu/x86_64-softmmu'
> make[1]: *** [subdir-x86_64-softmmu] Error 2
> make[1]: Leaving directory
> `/home/vivierl/Projects/KVM/kvm-userspace/qemu'
> make: *** [qemu] Error 2
> 
> Any idea ?
> 

Please do another pull, it was temporary broken yesterday.
Dor

> Laurent
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 1354 bytes --]

Le lundi 07 janvier 2008 à 15:26 +0200, Dor Laor a écrit :
> On Mon, 2008-01-07 at 14:14 +0100, Laurent Vivier wrote:
> > The error is:
> > 
> > libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_access_report':
> > /home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:221:
> > undefined reference to `kvm_enable_vapic'
> > libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup':
> > /home/vivierl/Projects/KVM/kvm-userspace/qemu/kvm-tpr-opt.c:287:
> > undefined reference to `kvm_enable_tpr_access_reporting'
> > collect2: ld returned 1 exit status
> > make[2]: *** [qemu-system-x86_64] Error 1
> > make[2]: Leaving directory
> > `/home/vivierl/Projects/KVM/kvm-userspace/qemu/x86_64-softmmu'
> > make[1]: *** [subdir-x86_64-softmmu] Error 2
> > make[1]: Leaving directory
> > `/home/vivierl/Projects/KVM/kvm-userspace/qemu'
> > make: *** [qemu] Error 2
> > 
> > Any idea ?
> > 
> 
> Please do another pull, it was temporary broken yesterday.
> Dor

Thank you for the answer Dor,

but a pull doesn't resolve anything (the clone has the same effect).

Is the correction has been pushed... ?

Laurent
-- 
----------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-userspace fails to compile

[Avi Kivity]

Laurent Vivier wrote:
> but a pull doesn't resolve anything (the clone has the same effect).
>
> Is the correction has been pushed... ?
>
>   

Should be...

Perhaps a ./configure is needed.

What's your HEAD?  I have a5b3d2c9b4d4ca3e02f294d14c7df016e070bda7, 
which compiles fine.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

Le lundi 07 janvier 2008 à 15:57 +0200, Avi Kivity a écrit :
> Laurent Vivier wrote:
> > but a pull doesn't resolve anything (the clone has the same effect).
> >
> > Is the correction has been pushed... ?
> >
> >   
> 
> Should be...
> 
> Perhaps a ./configure is needed.
> 
> What's your HEAD?  I have a5b3d2c9b4d4ca3e02f294d14c7df016e070bda7, 
> which compiles fine.

OK, I found where is the problem: my KERNELDIR is not the good one.

Thank you for the answers.

Laurent
-- 
----------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-userspace fails to compile

[Christoph Hellwig]

On Mon, Jan 07, 2008 at 03:25:50PM +0100, Laurent Vivier wrote:
> > Perhaps a ./configure is needed.
> > 
> > What's your HEAD?  I have a5b3d2c9b4d4ca3e02f294d14c7df016e070bda7, 
> > which compiles fine.
> 
> OK, I found where is the problem: my KERNELDIR is not the good one.
> 
> Thank you for the answers.

Looks like you were hitting the same problem that I did.  So what's the
correct KERNELDIR?  Care to post your ./configure line?

I have to add that having compile of userspace code depend on a kernel
dir is completely broken.  Any chance the kvm maintainers can fix
userspace code to compile standalone and not depend on a kernel?  Best
would be to have userspace and the standalone kernel module in entirely
different repositories.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Avi Kivity]

Christoph Hellwig wrote:
> I have to add that having compile of userspace code depend on a kernel
> dir is completely broken.  Any chance the kvm maintainers can fix
> userspace code to compile standalone and not depend on a kernel?  

That's the plan, but since things work for most people that area is not 
seeing much attention.  The problem areas are compiling userspace 
against older kernels, and that's not something we do often.

> Best
> would be to have userspace and the standalone kernel module in entirely
> different repositories.
>   

The standalone kernel module is actually not kept in source control; 
instead it is generated by copying the files from a standard kernel tree 
and gently massaging them with a big hammer.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Laurent Vivier]

[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]

Le mardi 15 janvier 2008 à 15:49 +0000, Christoph Hellwig a écrit :
> On Mon, Jan 07, 2008 at 03:25:50PM +0100, Laurent Vivier wrote:
> > > Perhaps a ./configure is needed.
> > > 
> > > What's your HEAD?  I have a5b3d2c9b4d4ca3e02f294d14c7df016e070bda7, 
> > > which compiles fine.
> > 
> > OK, I found where is the problem: my KERNELDIR is not the good one.
> > 
> > Thank you for the answers.
> 
> Looks like you were hitting the same problem that I did.  So what's the
> correct KERNELDIR?  Care to post your ./configure line?

It was where I put my KVM kernel sources, for instance:

KERNELDIR=/home/vivierl/Projects/KVM/kvm

generated by:

./configure --kerneldir=/home/vivierl/Projects/KVM/kvm \
--with-patched-kernel

ls /home/vivierl/Projects/KVM/kvm

arch     Documentation  ipc          Makefile        REPORTING-BUGS
System.map
block    drivers        Kbuild       mm              samples         usr
COPYING  fs             kernel       Module.symvers  scripts
virt
CREDITS  include        lib          net             security
vmlinux
crypto   init           MAINTAINERS  README          sound
vmlinux.o

		
> I have to add that having compile of userspace code depend on a kernel
> dir is completely broken.  Any chance the kvm maintainers can fix
> userspace code to compile standalone and not depend on a kernel?  Best
> would be to have userspace and the standalone kernel module in entirely
> different repositories.

Regards,
Laurent
-- 
----------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org  ------------------
  "La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: kvm-userspace fails to compile

[Christoph Hellwig]

On Tue, Jan 15, 2008 at 05:55:20PM +0200, Avi Kivity wrote:
> That's the plan, but since things work for most people that area is not 
> seeing much attention.  The problem areas are compiling userspace against 
> older kernels, and that's not something we do often.

Well, the point is there should be no compiling against older kernels or
kernels in general.  A userspace tarball should be entirely
self-contained and not care about any kind of kerneldir or similar.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Avi Kivity]

Christoph Hellwig wrote:
> On Tue, Jan 15, 2008 at 05:55:20PM +0200, Avi Kivity wrote:
>   
>> That's the plan, but since things work for most people that area is not 
>> seeing much attention.  The problem areas are compiling userspace against 
>> older kernels, and that's not something we do often.
>>     
>
> Well, the point is there should be no compiling against older kernels or
> kernels in general.  A userspace tarball should be entirely
> self-contained and not care about any kind of kerneldir or similar.
>
>   

Yes, you're right.  My confusion arose because we have two distinct 
needs for a "kernel directory":

1. A build directory for the external module (which really needs to be a 
kernel directory)
2. A directory with the exported userspace headers (like /usr/include)

We are using one directory for both.  Once we separate this, the mess 
should be cleared up.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: kvm-userspace fails to compile

[Christoph Hellwig]

On Tue, Jan 15, 2008 at 07:44:09PM +0200, Avi Kivity wrote:
> Yes, you're right.  My confusion arose because we have two distinct needs 
> for a "kernel directory":
>
> 1. A build directory for the external module (which really needs to be a 
> kernel directory)
> 2. A directory with the exported userspace headers (like /usr/include)
>
> We are using one directory for both.  Once we separate this, the mess 
> should be cleared up.

Exactly.  Please just bundle the latest required interface headers with
the userspace tarball.  Take e.g. xfs as an example.  This one doesn't
just need the whole filesystem layer but also quite a few lowlevel
implementation files that are used in libxfs through an kernel API shim
layer.  Instead of having some fragile dependencies it just ships copies
of the kernel files in exactly the version it needs.  Resyncing is quite
trivial and can be automated with a script.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/