[ open-vm-tools-Tracker-2900231 ] open-vm-tools: compile error at modules/linux

[SourceForge.net <no...@so...>]

Tracker item #2900231, was opened at 2009-11-18 18:27
Message generated for change (Comment added) made by archwndas
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: Open
Resolution: None
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: 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