Menu
▾
▴
open-vm-tools-devel — List for open-vm-tools developer discussions.
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(30) |
Oct
(50) |
Nov
(42) |
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(36) |
Feb
(13) |
Mar
(74) |
Apr
(17) |
May
(62) |
Jun
(53) |
Jul
(32) |
Aug
(58) |
Sep
(44) |
Oct
(21) |
Nov
(35) |
Dec
(53) |
| 2009 |
Jan
(43) |
Feb
(58) |
Mar
(14) |
Apr
(16) |
May
(61) |
Jun
(49) |
Jul
(11) |
Aug
(22) |
Sep
(37) |
Oct
(12) |
Nov
(23) |
Dec
(10) |
| 2010 |
Jan
(21) |
Feb
(13) |
Mar
(5) |
Apr
(18) |
May
(14) |
Jun
(10) |
Jul
(1) |
Aug
|
Sep
(13) |
Oct
(8) |
Nov
(11) |
Dec
(14) |
| 2011 |
Jan
(13) |
Feb
(19) |
Mar
(16) |
Apr
(10) |
May
(22) |
Jun
(4) |
Jul
(63) |
Aug
(14) |
Sep
(10) |
Oct
(12) |
Nov
(10) |
Dec
(43) |
| 2012 |
Jan
(3) |
Feb
(4) |
Mar
(35) |
Apr
(1) |
May
(32) |
Jun
(8) |
Jul
(10) |
Aug
(6) |
Sep
(3) |
Oct
(25) |
Nov
(14) |
Dec
(4) |
| 2013 |
Jan
(12) |
Feb
(6) |
Mar
(15) |
Apr
(24) |
May
(9) |
Jun
(2) |
Jul
|
Aug
(4) |
Sep
|
Oct
(8) |
Nov
(3) |
Dec
|
| 2014 |
Jan
(5) |
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2015 |
Jan
|
Feb
(5) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(5) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2009-11-20 06:58:40
|
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 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 |
|
From: SourceForge.net <no...@so...> - 2009-11-20 06:37:54
|
Tracker item #2900231, was opened at 2009-11-18 19:27 Message generated for change (Comment added) made by danielibarnes 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: Daniel Barnes (danielibarnes) Date: 2009-11-19 23: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 22: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 22: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 22: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 22: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 16: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 16: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 |
|
From: SourceForge.net <no...@so...> - 2009-11-20 05:57:44
|
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: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 |
|
From: SourceForge.net <no...@so...> - 2009-11-20 05:48:05
|
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: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 |
|
From: SourceForge.net <no...@so...> - 2009-11-20 05:45:07
|
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 |
|
From: SourceForge.net <no...@so...> - 2009-11-20 05:44:21
|
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: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 |
|
From: SourceForge.net <no...@so...> - 2009-11-19 23:46:57
|
Tracker item #2900231, was opened at 2009-11-18 19:27 Message generated for change (Comment added) made by danielibarnes 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: Daniel Barnes (danielibarnes) Date: 2009-11-19 16: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 16: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 |
|
From: SourceForge.net <no...@so...> - 2009-11-19 23:00:19
|
Tracker item #2900231, was opened at 2009-11-18 18:27 Message generated for change (Comment added) 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: 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: 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 |
|
From: SourceForge.net <no...@so...> - 2009-11-19 02:27:07
|
Tracker item #2900231, was opened at 2009-11-18 18:27 Message generated for change (Tracker Item Submitted) 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2900231&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-11-18 18:37:23
|
Tracker item #2899975, was opened at 2009-11-18 19:33 Message generated for change (Comment added) made by fabienthomas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&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: kernel modules Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Fabien Thomas (fabienthomas) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD vmxnet dont work after ifconfig down Initial Comment: As soon as one ifconfig vnx0 down is done the interface will not work again until the VM is rebooted ---------------------------------------------------------------------- >Comment By: Fabien Thomas (fabienthomas) Date: 2009-11-18 19:37 Message: Tested with latest git version. 18/11/2009 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-11-18 18:36:10
|
Tracker item #2899975, was opened at 2009-11-18 19:33 Message generated for change (Settings changed) made by fabienthomas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&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: kernel modules Group: None Status: Open Resolution: None >Priority: 9 Private: No Submitted By: Fabien Thomas (fabienthomas) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD vmxnet dont work after ifconfig down Initial Comment: As soon as one ifconfig vnx0 down is done the interface will not work again until the VM is rebooted ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-11-18 18:35:29
|
Tracker item #2899978, was opened at 2009-11-18 19:35 Message generated for change (Tracker Item Submitted) made by fabienthomas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899978&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: kernel modules Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Fabien Thomas (fabienthomas) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD vmxnet dont support setting mac address. Initial Comment: The module for freebsd dont have the code for mac address setting. I've done a small patch to support it but this have exposed another issue: the mac address set will not be resetted to default when the VM reboot. It will need a full shutdown / restart cycle. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899978&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-11-18 18:33:06
|
Tracker item #2899975, was opened at 2009-11-18 19:33 Message generated for change (Tracker Item Submitted) made by fabienthomas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Fabien Thomas (fabienthomas) Assigned to: Nobody/Anonymous (nobody) Summary: FreeBSD vmxnet dont work after ifconfig down Initial Comment: As soon as one ifconfig vnx0 down is done the interface will not work again until the VM is rebooted ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2899975&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-11-14 23:32:33
|
Tracker item #1813024, was opened at 2007-10-13 15:05 Message generated for change (Comment added) made by archwyvern You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1813024&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: checkvm Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: checkvm compile fails Initial Comment: Checkvm fails to compile (see error message below). ./configure --prefix=/usr --disable-multimon --without-x make LDFLAGS=-liconv all Unfortunately upgrading to a newer gcc is at the moment not possible. Regards Heiko Zuerker http://www.devil-linux.org ----------------------------------- gcc -v Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.2/specs Configured with: ../gcc-3.3.2/configure --prefix=/usr --localstatedir=/var --enable-shared --enable-CONFIG_SHELL=/bin/bash --enable-threads=posix --with-slibdir=/lib --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,objc --disable-nls i586-pc-linux-gnu Thread model: posix gcc version 3.3.2 ----------------------------------- ld -v GNU ld version 2.16.1 ----------------------------------- glibc 2.3.2 ----------------------------------- [ cut the stuff with worked ] make[1]: Entering directory `/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/checkvm' gcc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" -DPACKAGE_VERSION=\"2007.10.08-SNAPSHOT\" -DPACKAGE_STRING=\"open-vm-tools\ 2007.10.08-SNAPSHOT\" -DPACKAGE_BUGREPORT=\"ope...@li...\" -DPACKAGE=\"open-vm-tools\" -DVERSION=\"2007.10.08-SNAPSHOT\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DX_DISPLAY_MISSING=1 -DHAVE_ECVT=1 -DHAVE_FCVT=1 -DHAVE_WCHAR_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_CRYPT_H=1 -DHAVE_SYS_IO_H=1 -DHAVE_SYS_SYSINFO_H=1 -DHAVE_SYS_VFS_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_LSEEK=1 -DNO_MULTIMON=1 -I. -Wall -Werror -Wno-unknown-pragmas -Wno-uninitialized -fno-strict-aliasing -Wno-unused-value -DVMX86_TOOLS -I/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/lib/include -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -DUSING_AUTOCONF=1 -MT checkvm.o -MD -MP -MF .deps/checkvm.Tpo -c -o checkvm.o checkvm.c checkvm.c: In function `getVersion': checkvm.c:80: error: can't find a register in class `BREG' while reloading `asm' make[1]: *** [checkvm.o] Error 1 make[1]: Leaving directory `/data/build/tmp/open-vm-tools-2007.10.08-SNAPSHOT/checkvm' make: *** [all-recursive] Error 1 ---------------------------------------------------------------------- Comment By: No Name (archwyvern) Date: 2009-11-14 15:32 Message: Patch available @ http://bugs.gentoo.org/show_bug.cgi?id=200376 in comment #49. ---------------------------------------------------------------------- Comment By: Adar Dembo (adembo) Date: 2008-11-24 02:32 Message: Mike, we haven't added -nopie upstream, but enough people have complained about this (here and in the Gentoo bug report) that we should look into doing just that, or look at changing the affected checkvm.c code. I'll reopen this bug. For those seeing this bug report for the first time, there's a lot more information available at the associated Gentoo bug report, which can be found here: http://bugs.gentoo.org/show_bug.cgi?id=200376 ---------------------------------------------------------------------- Comment By: Mike Auty (ikelos) Date: 2007-11-26 11:04 Message: Logged In: YES user_id=230582 Originator: NO Sorry to check on this, but does that mean that -nopie has been added to the CFLAGS in the Makefile, or could other users still run into this problem? If it has been added, is it enabled at all times, or just when being built against a hardened config? Certainly for the Gentoo distribution we can add in a Makefile patch, I just would have thought it more beneficial to have a solid fix upstream... ---------------------------------------------------------------------- Comment By: ECL (sopwith) Date: 2007-11-26 10:38 Message: Logged In: YES user_id=18318 Originator: NO Closing as "WORKSFORME"... ---------------------------------------------------------------------- Comment By: Heiko Zuerker (smiley73) Date: 2007-11-26 09:23 Message: Logged In: YES user_id=112133 Originator: YES Hey, I ended up using this to get the compile running: CC="gcc -U_FORTIFY_SOURCE -fno-PIE" LDFLAGS=-liconv ./configure --prefix=/usr --without-x make all modules -U_FORTIFY_SOURCE was necessary because there are a lot of compiler warnings and we treat warnings as errors. -fno-PIE was necessary because of the error in the original support request. It may be required on hardened systems in general. Devil-Linux uses the hardened settings from "Hardened Linux from Scratch", which may be the base or similar to other hardened distros. Heiko ---------------------------------------------------------------------- Comment By: Mike Auty (ikelos) Date: 2007-11-26 04:24 Message: Logged In: YES user_id=230582 Originator: NO Hiya, we've had a report of one of our users patching the Makefile in checkvm to include I tried to CFLAGS+="-nopie" and this appears to solve the problem. It would be nice to find a way of only enabling this if required... ---------------------------------------------------------------------- Comment By: Heiko Zuerker (smiley73) Date: 2007-10-16 14:06 Message: Logged In: YES user_id=112133 Originator: YES I hate to admit it, but the problem seems to be Devil-Linux specific. I disabled all security features and now it compiles fine. I'm not sure where the problem is, this may take quite some time to figure it out. It may be SSP or PIE related. If you want you can close this tracker. Heiko ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=1813024&group_id=204462 |
|
From: Chris R. <chr...@ma...> - 2009-10-30 20:46:30
|
On 30 Oct 2009, at 20:31, Dmitry Torokhov wrote: > Hi Chris, > > On Friday 30 October 2009 12:37:18 pm Chris Ridd wrote: >> I copied some text from the OpenSolaris guest and pasted it into the >> Mac host. That certainly didn't work before! > > Yes, you need vmware_user running to be able to do copy/paste and DnD. > >> I couldn't get copy/paste >> working in the other direction, but X11 has a pretty weird concept of >> copy/paste so that could be down to user error. > > It works on Linux so (barring the bugs in the code) it should work > on Solaris > as well. OK, so I've definitely got something that half works :-) >> vmware-checkvm outputs "VMware software version 6 (good)". >> >> Is there any interest in my patches? >> > > Yes, we are certainly interested. However for us to be able to > integrate your > patches directly into our tree we need you to sign a contribution > agreement > (see http://open-vm-tools.sourceforge.net/contribute.php). Great, I'll try and figure out how to get the agreement over to you. Cheers, Chris |
|
From: Dmitry T. <dt...@vm...> - 2009-10-30 20:38:43
|
Hi Chris, On Friday 30 October 2009 12:37:18 pm Chris Ridd wrote: > On 30 Oct 2009, at 15:26, Chris Ridd wrote: > > Hi, > > > > I've been hacking on a set of patches which make open-vm-tools build > > against the GTK+ libraries shipped in OpenSolaris. The patches aren't > > too invasive, but I do need to clean them up a bit. I also haven't > > tried installing them into a boot environment so they may explode > > rather badly... > > When I wrote GTK+ I meant GTKMM instead, ie the C++ libraries for GTK. > Sorry for the confusion. > > Well the bits I installed into a new boot environment didn't explode > at all, but it isn't clear if things are working properly. > > VMware Fusion 3 thinks that the tools aren't installed. > > I ran 'pfexec vmtoolsd' in the background, and then vmware-user once > I'd logged into GNOME. They seemed happy to run and stay running. > > I copied some text from the OpenSolaris guest and pasted it into the > Mac host. That certainly didn't work before! Yes, you need vmware_user running to be able to do copy/paste and DnD. > I couldn't get copy/paste > working in the other direction, but X11 has a pretty weird concept of > copy/paste so that could be down to user error. It works on Linux so (barring the bugs in the code) it should work on Solaris as well. > > vmware-checkvm outputs "VMware software version 6 (good)". > > Is there any interest in my patches? > Yes, we are certainly interested. However for us to be able to integrate your patches directly into our tree we need you to sign a contribution agreement (see http://open-vm-tools.sourceforge.net/contribute.php). Thanks! -- Dmitry |
|
From: Chris R. <chr...@ma...> - 2009-10-30 19:37:35
|
On 30 Oct 2009, at 15:26, Chris Ridd wrote: > Hi, > > I've been hacking on a set of patches which make open-vm-tools build > against the GTK+ libraries shipped in OpenSolaris. The patches aren't > too invasive, but I do need to clean them up a bit. I also haven't > tried installing them into a boot environment so they may explode > rather badly... When I wrote GTK+ I meant GTKMM instead, ie the C++ libraries for GTK. Sorry for the confusion. Well the bits I installed into a new boot environment didn't explode at all, but it isn't clear if things are working properly. VMware Fusion 3 thinks that the tools aren't installed. I ran 'pfexec vmtoolsd' in the background, and then vmware-user once I'd logged into GNOME. They seemed happy to run and stay running. I copied some text from the OpenSolaris guest and pasted it into the Mac host. That certainly didn't work before! I couldn't get copy/paste working in the other direction, but X11 has a pretty weird concept of copy/paste so that could be down to user error. vmware-checkvm outputs "VMware software version 6 (good)". Is there any interest in my patches? Cheers, Chris |
|
From: Chris R. <chr...@ma...> - 2009-10-30 15:27:27
|
Hi, I've been hacking on a set of patches which make open-vm-tools build against the GTK+ libraries shipped in OpenSolaris. The patches aren't too invasive, but I do need to clean them up a bit. I also haven't tried installing them into a boot environment so they may explode rather badly... But I did try running vmware-user by hand, and noticed it output "XXX: implement Id_SetRESUid" but appeared to keep running. Is this output a significant problem? Are there any thoughts on using things like Solaris privileges? Is this the right list to be sending patches? I didn't get any feedback on my DESTDIR patch. Cheers, Chris |
|
From: Chris R. <chr...@ma...> - 2009-10-29 06:17:56
|
On 29 Oct 2009, at 03:02, Ryan Beasley wrote: > On 10/28/2009 08:17 AM, Chris Ridd wrote: >> Now to find out why ghIntegrationX11.c no longer builds on >> OpenSolaris... > > Are you sure that it ever built there? The Open VM Tools have never > supported > Unity, aka the feature requiring ghIntegrationX11.c, on anything but > Linux guest > VMs. FreeBSD and Solaris users should run ./configure with -- > disable-unity. > > HTH. :) No I'm not sure it ever did build! I think I'd managed to successfully run configure and produce something that couldn't be built. A different set of configure arguments no longer attempts to compile that file... Cheers, Chris |
|
From: Ryan B. <rbe...@vm...> - 2009-10-29 03:02:24
|
On 10/28/2009 08:17 AM, Chris Ridd wrote: > Now to find out why ghIntegrationX11.c no longer builds on > OpenSolaris... Are you sure that it ever built there? The Open VM Tools have never supported Unity, aka the feature requiring ghIntegrationX11.c, on anything but Linux guest VMs. FreeBSD and Solaris users should run ./configure with --disable-unity. HTH. :) -- Ryan Beasley :: MTS, Guest Components - Applications :: VMware, Inc. |
|
From: Chris R. <chr...@ma...> - 2009-10-28 19:15:23
|
Hi, I noticed that "gmake install" on Solaris doesn't obey the DESTDIR variable for kernel modules. This seemed like something worth fixing, so please find attached a small patch. Cheers, Chris |
|
From: Chris R. <chr...@ma...> - 2009-10-28 15:17:20
|
Can the project's web page be updated slightly to indicate exactly how to clone the git repo? The "protocol" part is currently missing, so you have to guess that this works: git clone git://git.opensource.vmware.com/opensource/open-vm-tools/ Thanks! Now to find out why ghIntegrationX11.c no longer builds on OpenSolaris... Chris |
|
From: SourceForge.net <no...@so...> - 2009-10-22 23:23:03
|
Tracker item #2865799, was opened at 2009-09-24 08:25 Message generated for change (Comment added) made by mvanzin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2865799&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: libraries Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jim (pirzyk) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails Initial Comment: When compling 2009.09.18, the 'make install' target fails, can't create shared libraries because of misisng symbols. Had to add some tags in the configure.ac and */Makefile.am to get it to work. Patch attached. ---------------------------------------------------------------------- >Comment By: Marcelo Vanzin (mvanzin) Date: 2009-10-22 16:22 Message: I just tried the latest release on a Fedora 8 VM and it seems to work fine. This is the output of the step that seems to fail for you: libtool: install: (cd /home/vmware/ovt/open-vm-tools-2009.10.15-201664/tests/testDebug; /bin/sh /home/vmware/ovt/open-vm-tools-2009.10.15-201664/libtool --tag CC --mode=relink gcc -g -O2 -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -Wl,-z,defs -Wl,-lc -shared -module -avoid-version-o libtestDebug.la -rpath /usr/local/share/open-vm-tools/tests libtestDebug_la-testDebug.lo -lgobject-2.0 -lglib-2.0 /home/vmware/ovt/open-vm-tools-2009.10.15-201664/libvmtools/libvmtools.la -lglib-2.0 ../vmrpcdbg/libvmrpcdbg.la -inst-prefix-dir /home/vmware/ovt/inst) libtool: relink: gcc -shared .libs/libtestDebug_la-testDebug.o -Wl,--whole-archive ../vmrpcdbg/.libs/libvmrpcdbg.a -Wl,--no-whole-archive -Wl,-rpath -Wl,/usr/local/lib -lgobject-2.0 -lgmodule-2.0 -L/home/vmware/ovt/inst/usr/local/lib -L/usr/local/lib -lvmtools -ldl -lcrypt -lpthread -lglib-2.0 -Wl,-z -Wl,defs -Wl,-lc -Wl,-soname -Wl,libtestDebug.so -o .libs/libtestDebug.so libtool: install: /usr/bin/install -c .libs/libtestDebug.soT /home/vmware/ovt/inst/usr/local/share/open-vm-tools/tests/libtestDebug.so Are you sure you somehow don't have a mix of old and new sources you're trying to compile? (The functions that libtool complains about in your output have gone through some changes in the past few months.) I'd recommend trying with a fresh source dir. If you're getting the data from git, then there might be an issue with the version of libtool in those distros (since I used the tarball, it comes with the code generated from our version of libtool, which I think is 2.2). ---------------------------------------------------------------------- Comment By: Jim (pirzyk) Date: 2009-10-21 09:51 Message: In further testing, I have determined the problem only happens on the Fedora Core 5 and 8 systems I compile on, not on Fedora Core 11 or CentOS 5.3. Here's the errors: make[3]: Entering directory `/var/tmp/open-vm-tools-2009.10.15-201664/tests/testDebug' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/open-vm-tools/tests" || //bin/mkdir -p "/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/share/open-vm-tools/tests" /bin/sh ../../libtool --mode=install /usr/bin/install -c 'libtestDebug.la' '/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/share/open-vm-tools/tests/libtestDebug.la' libtool: install: warning: relinking `libtestDebug.la' libtool: install: (cd /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/testDebug; /bin/sh /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/libtool --tag CC --mode=relink gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -Wl,-z,defs -Wl,-lc -shared -module -avoid-version -o libtestDebug.la -rpath /usr/share/open-vm-tools/tests libtestDebug_la-testDebug.lo -lgobject-2.0 -lglib-2.0 /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/libvmtools/libvmtools.la -lglib-2.0 ../vmrpcdbg/libvmrpcdbg.la -inst-prefix-dir /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01) libtool: relink: gcc -shared .libs/libtestDebug_la-testDebug.o -Wl,--whole-archive ../vmrpcdbg/.libs/libvmrpcdbg.a -Wl,--no-whole-archive -lgobject-2.0 -L/usr/lib -lgmodule-2.0 -L/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/lib -lvmtools -ldl -ldnet -lcrypt -licui18n -licuuc -licudata -lpthread -lm -lglib-2.0 -m32 -march=i386 -mtune=generic -Wl,-z -Wl,defs -Wl,-lc -Wl,-soname -Wl,libtestDebug.so -o .libs/libtestDebug.so .libs/libtestDebug_la-testDebug.o: In function `TestDebugReceiveVersion': /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/testDebug/testDebug.c:165: undefined reference to `Util_SafeInternalStrdup' ../vmrpcdbg/.libs/libvmrpcdbg.a(libvmrpcdbg_la-debugChannel.o): In function `RpcDebugSend': /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:233: undefined reference to `Util_SafeInternalStrdup' /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:245: undefined reference to `Util_SafeInternalStrdup' /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:222: undefined reference to `Util_SafeInternalStrdup' collect2: ld returned 1 exit status libtool: install: error: relink `libtestDebug.la' with the above command before installing it make[3]: *** [install-pluginLTLIBRARIES] Error 1 make[3]: Leaving directory `/var/tmp/open-vm-tools-2009.10.15-201664/tests/testDebug' ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2009-09-24 17:21 Message: Could you post the error that you're seeing? It looks like there's something more fundamentally wrong here, because libMisc.la is already linked into libvmtools.so, which is already part of the libraries used by the testDebug plugin you're modifying. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2865799&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-10-21 16:51:15
|
Tracker item #2865799, was opened at 2009-09-24 11:25 Message generated for change (Comment added) made by pirzyk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2865799&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: libraries Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jim (pirzyk) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails Initial Comment: When compling 2009.09.18, the 'make install' target fails, can't create shared libraries because of misisng symbols. Had to add some tags in the configure.ac and */Makefile.am to get it to work. Patch attached. ---------------------------------------------------------------------- Comment By: Jim (pirzyk) Date: 2009-10-21 12:51 Message: In further testing, I have determined the problem only happens on the Fedora Core 5 and 8 systems I compile on, not on Fedora Core 11 or CentOS 5.3. Here's the errors: make[3]: Entering directory `/var/tmp/open-vm-tools-2009.10.15-201664/tests/testDebug' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/open-vm-tools/tests" || //bin/mkdir -p "/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/share/open-vm-tools/tests" /bin/sh ../../libtool --mode=install /usr/bin/install -c 'libtestDebug.la' '/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/share/open-vm-tools/tests/libtestDebug.la' libtool: install: warning: relinking `libtestDebug.la' libtool: install: (cd /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/testDebug; /bin/sh /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/libtool --tag CC --mode=relink gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -Wall -Werror -Wno-pointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uninitialized -Wl,-z,defs -Wl,-lc -shared -module -avoid-version -o libtestDebug.la -rpath /usr/share/open-vm-tools/tests libtestDebug_la-testDebug.lo -lgobject-2.0 -lglib-2.0 /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/libvmtools/libvmtools.la -lglib-2.0 ../vmrpcdbg/libvmrpcdbg.la -inst-prefix-dir /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01) libtool: relink: gcc -shared .libs/libtestDebug_la-testDebug.o -Wl,--whole-archive ../vmrpcdbg/.libs/libvmrpcdbg.a -Wl,--no-whole-archive -lgobject-2.0 -L/usr/lib -lgmodule-2.0 -L/home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664.1.fc5-jpirzy01/usr/lib -lvmtools -ldl -ldnet -lcrypt -licui18n -licuuc -licudata -lpthread -lm -lglib-2.0 -m32 -march=i386 -mtune=generic -Wl,-z -Wl,defs -Wl,-lc -Wl,-soname -Wl,libtestDebug.so -o .libs/libtestDebug.so .libs/libtestDebug_la-testDebug.o: In function `TestDebugReceiveVersion': /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/testDebug/testDebug.c:165: undefined reference to `Util_SafeInternalStrdup' ../vmrpcdbg/.libs/libvmrpcdbg.a(libvmrpcdbg_la-debugChannel.o): In function `RpcDebugSend': /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:233: undefined reference to `Util_SafeInternalStrdup' /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:245: undefined reference to `Util_SafeInternalStrdup' /home/jpirzy01/src/BUILD/open-vm-tools-2009.10.15-201664/tests/vmrpcdbg/debugChannel.c:222: undefined reference to `Util_SafeInternalStrdup' collect2: ld returned 1 exit status libtool: install: error: relink `libtestDebug.la' with the above command before installing it make[3]: *** [install-pluginLTLIBRARIES] Error 1 make[3]: Leaving directory `/var/tmp/open-vm-tools-2009.10.15-201664/tests/testDebug' ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2009-09-24 20:21 Message: Could you post the error that you're seeing? It looks like there's something more fundamentally wrong here, because libMisc.la is already linked into libvmtools.so, which is already part of the libraries used by the testDebug plugin you're modifying. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2865799&group_id=204462 |
|
From: SourceForge.net <no...@so...> - 2009-10-14 02:21:53
|
Tracker item #2658928, was opened at 2009-03-03 22:24 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2658928&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: kernel modules Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Sisternicky (eisiware) Assigned to: Nobody/Anonymous (nobody) Summary: vsock module not loadable into the kernel (2.6.28.7) Initial Comment: Hi, on my new kernel, the module vsock will not load. On modprobing, it returns the following error message: root [ ~ ]# modprobe -v vsock insmod /lib/modules/2.6.28.7/kernel/net/vsock/vsock.ko FATAL: Error inserting vsock (/lib/modules/2.6.28.7/kernel/net/vsock/vsock.ko): Unknown symbol in module, or unknown parameter (see dmesg) and here follows the kernel log: Mar 3 23:18:40 landfrauen kernel: [ 1912.571989] vsock: no symbol version for VMCIMemcpyToQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.572151] vsock: Unknown symbol VMCIMemcpyToQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.572285] vsock: no symbol version for VMCIEvent_Unsubscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.572382] vsock: Unknown symbol VMCIEvent_Unsubscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.572514] vsock: no symbol version for VMCIQueuePair_Alloc Mar 3 23:18:40 landfrauen kernel: [ 1912.572595] vsock: Unknown symbol VMCIQueuePair_Alloc Mar 3 23:18:40 landfrauen kernel: [ 1912.572864] vsock: no symbol version for VMCIDatagram_Send Mar 3 23:18:40 landfrauen kernel: [ 1912.572946] vsock: Unknown symbol VMCIDatagram_Send Mar 3 23:18:40 landfrauen kernel: [ 1912.572953] vsock: no symbol version for VMCI_GetContextID Mar 3 23:18:40 landfrauen kernel: [ 1912.572959] vsock: Unknown symbol VMCI_GetContextID Mar 3 23:18:40 landfrauen kernel: [ 1912.573510] vsock: no symbol version for VMCIQueuePair_Detach Mar 3 23:18:40 landfrauen kernel: [ 1912.573594] vsock: Unknown symbol VMCIQueuePair_Detach Mar 3 23:18:40 landfrauen kernel: [ 1912.573977] vsock: no symbol version for VMCIMemcpyFromQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.574062] vsock: Unknown symbol VMCIMemcpyFromQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.574395] vsock: no symbol version for VMCI_DeviceGet Mar 3 23:18:40 landfrauen kernel: [ 1912.574471] vsock: Unknown symbol VMCI_DeviceGet Mar 3 23:18:40 landfrauen kernel: [ 1912.574636] vsock: no symbol version for VMCIEvent_Subscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.574713] vsock: Unknown symbol VMCIEvent_Subscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.574947] vsock: no symbol version for VMCIDatagram_DestroyHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575027] vsock: Unknown symbol VMCIDatagram_DestroyHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575162] vsock: no symbol version for VMCIDatagram_CreateHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575240] vsock: Unknown symbol VMCIDatagram_CreateHnd all other modules load fine. Is there any fix known already? ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-10-14 02:21 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2009-09-30 00:22 Message: I'm pretty sure we've fixed the vsock / vmci symbol issues in the last several releases. Let me know if you still see this issue. ---------------------------------------------------------------------- Comment By: Sisternicky (eisiware) Date: 2009-03-04 22:32 Message: I'm using open-vm-tools-2009.02.18-148847 I did a toplevel build of the tools, the config.log is attached. File Added: config.log ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 21:48 Message: Also, what version of open-vm-tools are you using? ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 19:06 Message: Ok so we have established that it is a CONFIG_MODVERSIONS problem. Can you provide some more details about what steps you took to build the vsock module. Did you do a top level make in open-vm-tools or something else? I'd still like to get to the bottom of why you ended up with a module that wasn't built against VMCI symbols. ---------------------------------------------------------------------- Comment By: Sisternicky (eisiware) Date: 2009-03-04 16:42 Message: Yes, it does. My modules are modprobed by bootscript (all of the vmware modules), with vsock being last. ---------------------------------------------------------------------- Comment By: Giandomenico De Tullio (kheru) Date: 2009-03-04 14:36 Message: Are VMCI* symbols exported by vmci.ko module ?! If you modprobe vmci.ko BEFORE modprobe-ing vsock returns the same error? dependencies problem ?! ( depmod -a ? ^.- ) ---------------------------------------------------------------------- Comment By: Sisternicky (eisiware) Date: 2009-03-04 07:40 Message: Hi again, thanks for the quick answer. There is an (empty) Module.symvers file in the module build directory modprobe --dump-modversions ./vsock.ko: 0x4f8d5728 struct_module 0x7faa1013 release_sock 0x33c3a362 per_cpu__current_task 0x12da5bb2 __kmalloc 0x5e22aa50 sock_init_data 0xb279da12 pv_lock_ops 0xd42b7232 _write_unlock_bh 0x3f4d635c sock_no_setsockopt 0xc8b57c27 autoremove_wake_function 0xa1801a2e sock_no_getsockopt 0xbe447f76 sock_no_ioctl 0x973873ab _spin_lock 0x8949858b schedule_work 0x5acb8506 sock_queue_rcv_skb 0x6729d3df __get_user_4 0x47a346b3 skb_recv_datagram 0xed06ac02 sock_no_sendpage 0xbd31d52f sock_no_mmap 0x4ba758f9 misc_register 0x7afd8702 sock_no_socketpair 0x2254d547 sk_alloc 0xa2a1e5c9 _write_lock_bh 0xb72397d5 printk 0xc642a151 lock_sock_nested 0x2da418b5 copy_to_user 0xa8eb44f9 sock_no_listen 0xd2123419 sock_no_accept 0x293beace sk_free 0x748caf40 down 0xa368017a init_net 0x7dceceac capable 0x934b1816 proto_register 0xb2fd5ceb __put_user_4 0x85c9c6af __alloc_skb 0x82673561 schedule_delayed_work 0x3c9b4b67 sock_register 0xd62c833f schedule_timeout 0x7f8da821 kfree_skb 0x0fc26794 proto_unregister 0x88dff1b9 skb_copy_datagram_iovec 0x2253d3c5 sk_receive_skb 0x6111e1bc init_timer 0x57a6504e vsnprintf 0x3aa1dbcf _spin_unlock_bh 0x037a0cba kfree 0x0e762d6e request_module 0x33d92f9a prepare_to_wait 0x62737e1d sock_unregister 0x9fb3dd30 memcpy_fromiovec 0x3f1899f1 up 0x9ccb2622 finish_wait 0x08a56041 skb_dequeue 0x701d0ebd snprintf 0x93cbd1ec _spin_lock_bh 0xc5456b60 skb_put 0xf2a644fb copy_from_user 0xc5b0fa1a misc_deregister 0xb052f6a9 skb_free_datagram 0x0da10ec3 security_sock_graft and you are right :) with --force-modversion the module loads find. Hope the info helps. ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 00:08 Message: It sounds like you have a newer kernel built with CONFIG_MODVERSIONS and the vsock module doesn't know about the vmci module symbol versions so the kernel is refusing to load it. This should work ... I'm interested to figure out what went wrong. First let me say that you should be able to force the kernel to load the module by using --force-modversion (although then you bypass CONFIG_MODVERSIONS which we would like to avoid). Is there a Module.symvers file in the vsock module build directory? If so, what are the contents? What is the contents of the __versions section of the module? modprobe --dump-modversions ./vsock.ko should give the info. It would also be interesting to see the output of nm ./vmci.ko | grep __crc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2658928&group_id=204462 |
58 messages has been excluded from this view by a project administrator.
