Tracker item #2900231, was opened at 2009-11-18 18:27
Message generated for change (Settings changed) made by mvanzin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2900231&group_id=204462
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: misc
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Symeon Nifos (archwndas)
Assigned to: Nobody/Anonymous (nobody)
Summary: open-vm-tools: compile error at modules/linux
Initial Comment:
Hi, I was compiling after configure with:
./configure --with-procps="-L/lib/ -lproc-3.2.8"
First think I would like to point out is that you should not test the existence
of libproc by linking with the specific version number. I do not know about
other systems but in my Distribution (Sabayon Linux 5.0 x86_64)
# ls /lib/libproc* -la
-r-xr-xr-x 1 root root 64160 2009-07-23 15:15 /lib/libproc-3.2.8.so
lrwxrwxrwx 1 root root 16 2009-08-08 12:32 /lib/libproc.so ->
libproc-3.2.8.so
so if in the configure script you link with -L/lib -lproc, configure would not
stop reporting a missing library libproc or something like that. Another issue
I encountered is during the compilation the header file:
/usr/include/X11/extensions/saver.h was missing because the corresponding
package was not installed in my system. The package in my Sabayon (Gentoo based
Distribution) is called x11-proto/scrnsaverproto-1.1.0. I had to install that
before the compilation can go on. This should have been reported in the
configuration stage and not in the building stage.
The building stage stops where you see below with the following error message:
Using standalone build system.
make[2]: Entering directory
`/common/src/open-vm-tools-2009.11.17-210370/modules/linux/vmmemctl'
Makefile:163: Makefile.normal: No such file or directory
make[2]: *** No rule to make target `Makefile.normal'. Stop.
make[2]: Leaving directory
`/common/src/open-vm-tools-2009.11.17-210370/modules/linux/vmmemctl'
make[1]: *** [vmmemctl] Error 2
make[1]: Leaving directory `/common/src/open-vm-tools-2009.11.17-210370/modules'
make: *** [all-recursive] Error 1
Any ideas?
----------------------------------------------------------------------
>Comment By: Marcelo Vanzin (mvanzin)
Date: 2009-12-18 18:02
Message:
The new release has better handling of libproc and scrnsaver.h. You didn't
come back on the kernel issue so I'll assume one of the suggested
workarounds worked.
----------------------------------------------------------------------
Comment By: Marcelo Vanzin (mvanzin)
Date: 2009-11-20 10:51
Message:
Man, slow down.
About saver.h: open-vm-tools code does not include saver.h.
$ grep -r saver.h .
./lib/unity/unityX11.h:#include <X11/extensions/scrnsaver.h>
So it seems that one of the headers we do include ends up including
saver.h. And what that tells me is that your distro's packages are broken:
they're installing a dev package that needs saver.h, but it's missing a
dependency saying that the package providing saver.h should be installed. I
don't think this is something that open-vm-tools should try to work
around.
glib 2.6.0: that glib is OLD. I'd be surprised if your distro doesn't have
it. You're most probably missing the devel packages for it.
kernel headers: if your headers are not in /lib/modules/$(uname -r), try
to pass "--with-linuxdir" in the configure command line and point it to the
right place.
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-20 00:35
Message:
sources were not there and it could not compile without them. The headers
were there originally but it would still not compile. That is why I told
you that I had to install the sources.
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-20 00:34
Message:
I tried to install the latest version of open-vm-tools but I get during
configuration
a dependency error: glib >= 2.6.0 required
any version of open-vm-tools that needs an older glib, just to try out?
----------------------------------------------------------------------
Comment By: Daniel Barnes (danielibarnes)
Date: 2009-11-19 23:17
Message:
sources != headers
Open sulfur and look for "sys-kernel/linux-headers-2.6.31"
As for running open-vm-tools in an OpenSolaris guest, you'll need to
compile it under OpenSolaris. I've never tried that, myself. I've only
compiled for Linux guests.
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-19 22:58
Message:
No the problem is not that. The kernel sources were not installed. I
realized that the package manager of my distro provides them and I could
not install them unless I installed the kernel sources first. But what I do
not understand is how I use them. Whatever I am trying to run it says that
it should be run from inside a virtual machine. But if I am running inside
a virtual machine, the guest operating system cannot see my Linux host and
run the open tools? Suppose I am running OpenSolaris 2009/06 as guest
operating system in my linux host with in vmware workstation. How could I
activate the open vmware tools for this OpenSolaris guest?
----------------------------------------------------------------------
Comment By: Daniel Barnes (danielibarnes)
Date: 2009-11-19 22:37
Message:
The missing Makefile.normal isn't the problem, it's a symptom. The problem
is likely that you don't have linux headers under
/lib/modules/2.6.31-sabayon/build/include.
One of two cases is likely true: 1) The headers are not installed, or 2)
The headers are in /lib/modules/2.6.31/build/include and you just need a
softlink:
ln -s ../2.6.31/build /lib/modules/2.6.31-sabayon/
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-19 21:57
Message:
The problem is that Makefile.normal is missing. It should be in
# grep "Makefile.normal" ./ -r -i -I
./modules/linux/vmci/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmxnet3/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmxnet/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmsync/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmmemctl/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/pvscsi/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmblock/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vsock/Makefile:include $(SRCROOT)/Makefile.normal
./modules/linux/vmhgfs/Makefile:include $(SRCROOT)/Makefile.normal
where:
vmmemctl # grep "SRCROOT" ./ -r -i -I
./Makefile:#### SRCROOT _must_ be a relative path.
./Makefile:SRCROOT = .
./Makefile:AUTOCONF_DIR := $(SRCROOT)/shared/autoconf
./Makefile:INCLUDE += -I$(SRCROOT)/shared
./Makefile: cp -f $< $(SRCROOT)/../$(DRIVER).o
./Makefile: make -C $(BUILD_DIR) SUBDIRS=$$PWD
SRCROOT=$$PWD/$(SRCROOT) \
./Makefile: make -C $$PWD SRCROOT=$$PWD/$(SRCROOT) \
./Makefile:include $(SRCROOT)/Makefile.kernel
./Makefile:include $(SRCROOT)/Makefile.normal
./Makefile.kernel:$(DRIVER)-y := $(subst $(SRCROOT)/, , $(patsubst %.c,
%.o, $(wildcard $(SRCROOT)/*.c)))
./Makefile.kernel:VMMEMCTL_PATH := $(shell cd $(SRCROOT) && pwd)
panormitis vmmemctl # ls
COPYING Makefile Makefile.kernel os.c README vmmemctl_version.h
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-19 21:48
Message:
Making all in modules
make[1]: Entering directory
`/common/src/open-vm-tools-2009.11.17-210370/modules'
make VM_UNAME=2.6.31-sabayon MV=mv RM=rm \
OVT_SOURCE_DIR=/common/src/open-vm-tools-2009.11.17-210370
\
MODULEBUILDDIR=/common/src/open-vm-tools-2009.11.17-210370/modules/linux
\
-C
"/common/src/open-vm-tools-2009.11.17-210370/modules/linux/vmmemctl"
Using standalone build system.
make[2]: Entering directory
`/common/src/open-vm-tools-2009.11.17-210370/modules/linux/vmmemctl'
Makefile:163: Makefile.normal: No such file or directory
make[2]: *** No rule to make target `Makefile.normal'. Stop.
make[2]: Leaving directory
`/common/src/open-vm-tools-2009.11.17-210370/modules/linux/vmmemctl'
make[1]: *** [vmmemctl] Error 2
make[1]: Leaving directory
`/common/src/open-vm-tools-2009.11.17-210370/modules'
make: *** [all-recursive] Error 1
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-19 21:45
Message:
$ ls /usr/include/X11/extensions/sa*
/usr/include/X11/extensions/saver.h
/usr/include/X11/extensions/saverproto.h
----------------------------------------------------------------------
Comment By: Symeon Nifos (archwndas)
Date: 2009-11-19 21:44
Message:
This is my kernel:
Linux archwn 2.6.31-sabayon #1 SMP Tue Nov 17 19:06:22 UTC 2009 x86_64
Intel(R) Core(TM)2 Duo CPU P9700 @ 2.80GHz GenuineIntel GNU/Linux
----------------------------------------------------------------------
Comment By: Daniel Barnes (danielibarnes)
Date: 2009-11-19 15:46
Message:
procps: I had the same problem. My workaround was to use sed to edit the
configure script prior to running it.
build error: I had this problem also. The Makefiles for each module look
for kernel headers in the /lib/modules/$(uname -r)/build/include directory.
Make sure it exists.
----------------------------------------------------------------------
Comment By: Marcelo Vanzin (mvanzin)
Date: 2009-11-19 15:00
Message:
. procps: I'll take a look.
. do you mean X11/extensions/scrnsaver.h? There are no references to
"saver.h" in the sources.
. what kernel are you compiling against and where are the headers? On my
Ubuntu box I see the "Using 2.6.x kernel build system." instead of the one
you see ("Using standalone build system."), so something seems odd about
your environment.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2900231&group_id=204462
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
