Gentoo Forums :: View topic - vmware-modules-1.0.0.15-r1 fails to compile on 2.6.25

vmware-modules-1.0.0.15-r1 fails to compile on 2.6.25

View unanswered posts
View posts from last 24 hours

Gentoo Forums Forum Index

Other Things Gentoo

View previous topic :: View next topic

Author

Message

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Thu Apr 17, 2008 10:30 pm Post subject: vmware-modules-1.0.0.15-r1 fails to compile on 2.6.25

hi,

is this a problem with the new kernel? i am unsure.

Code:

xeon ~ # emerge -1 "=vmware-modules-1.0.0.15-r1"
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.15-r1 to /
* vmware-any-any-update115.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking vmware-any-any-update115.tar.gz ;-) ... [ ok ]
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 2.6.25-gentoo-blackbit
>>> Unpacking source...
>>> Unpacking vmware-any-any-update115.tar.gz to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
>>> Unpacking ./vmware-any-any-update115/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
* Applying various patches (bugfixes/updates) ...
* 000_all_makefile-include-directory.patch ... [ ok ]
* 020_all_epoll-def-warnings.patch ... [ ok ]
* Done with patching
* Applying various patches (bugfixes/updates) ...
* 030_all_fix-linux-headers.patch ... [ ok ]
* Done with patching
* Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ]
>>> Unpacking ./vmware-any-any-update115/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
* Applying various patches (bugfixes/updates) ...
* 000_all_makefile-include-directory.patch ... [ ok ]
* 020_all_epoll-def-warnings.patch ... [ ok ]
* Done with patching
* Applying various patches (bugfixes/updates) ...
* 021_all_wireless_fix.patch ... [ ok ]
* Done with patching
* Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work ...
* Preparing vmmon module
Using 2.6.x kernel build system.
make -C /usr/src/linux/include/.. M=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.25-gentoo'
make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driverLog.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/hostif.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/comport.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/cpuid.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/hash.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/memtrack.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/phystrack.o
CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task.o
cc1plus: warning: command line option "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/hostKernel.h:56,
from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task.c:30:
include/asm/page.h: In function ‘pte_t native_make_pte(pteval_t)’:
include/asm/page.h:128: error: expected primary-expression before ‘)’ token
include/asm/page.h:128: error: expected ‘;’ before ‘{’ token
include/asm/page.h:128: error: expected primary-expression before ‘.’ token
include/asm/page.h:128: error: expected `;' before ‘}’ token
make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.25-gentoo'
make: *** [vmmon.ko] Error 2
*
* ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3202: Called linux-mod_src_compile
* environment, line 2421: Called die
* The specific snippet of code:
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CC=\"$(get-KERNEL_CC)\" L
DFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${
BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CC="
$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
* The die message:
* Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CC=i686-pc-linux-gnu-gcc LDFLAGS= auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/u
sr/src/linux KBUILD_OUTPUT=/usr/src/linux
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/temp/environment'.
*
xeon ~ #

include/asm/page.h lines 126-129:

Code:

static inline pte_t native_make_pte(pteval_t val)
{
return (pte_t) { .pte = val };
}

Desintegr
l33t
l33t

Joined: 25 Mar 2004
Posts: 863
Location: France - Orléans

Posted: Thu Apr 17, 2008 10:32 pm Post subject:

Try vmware-modules-1.0.0.17-r1. _________________ Gentoo ~AMD64 Hoc Volo, Sic Jubeo ! Mon wiki : http://desintegr.free.fr

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Fri Apr 18, 2008 2:43 pm Post subject:

i am using vmware-server-1.0.5.80187, which needs

Code:

!<app-emulation/vmware-modules-1.0.0.15
!>=app-emulation/vmware-modules-1.0.0.16

Desintegr
l33t
l33t

Joined: 25 Mar 2004
Posts: 863
Location: France - Orléans

Posted: Fri Apr 18, 2008 2:50 pm Post subject:

So do not use kernel 2.6.25 and wait for a patch. You can add yourself to CC for bug 218250. _________________ Gentoo ~AMD64 Hoc Volo, Sic Jubeo ! Mon wiki : http://desintegr.free.fr

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Sat Apr 19, 2008 12:37 am Post subject:

thx for the link

Link31
Apprentice

Joined: 17 Apr 2006
Posts: 200
Location: France

Posted: Sat Apr 19, 2008 12:50 am Post subject:

As a temporary fix, you can try this:

- create an overlay for vmware-modules-1.0.0.15-r1

- edit these files as follows:

files/patches/vmmon/030_all_fix-linux-headers.patch

Code:

diff -uNr vmmon-only.old/include/vcpuset.h vmmon-only/include/vcpuset.h
--- vmmon-only.old/include/vcpuset.h 2007-07-22 12:21:17.000000000 +0100
+++ vmmon-only/include/vcpuset.h 2007-12-01 15:52:11.000000000 +0000
@@ -71,7 +71,7 @@
#define ffs(x) ffs_x86_64(x)

#elif defined MODULE
- #include "asm/bitops.h"
+ #include "linux/bitops.h"
#elif defined __APPLE__ && defined KERNEL
/*
* XXXMACOS An ugly hack to resolve redefinition of PAGE_ defines
diff -ubBr vmmon-only.old/common/task.c vmmon-only/common/task.c
--- vmmon-only.old/common/task.c 2007-11-28 19:58:17.000000000 +0900
+++ vmmon-only/common/task.c 2008-03-24 22:39:29.000000000 +0900
@@ -25,7 +25,7 @@
* we do not need asm/page.h anymore in this file - not surprising, this
* is common file, yes? And Windows do not have page.h, do they?
*/
-#define _I386_PAGE_H
+#define _ASM_X86_PAGE_H
/* On Linux, must come before any inclusion of asm/page.h --hpreg */
#include "hostKernel.h"
#ifdef linux

files/patches/vmnet/021_all_wireless_fix.patch

Code:

diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
@@ -32,7 +32,7 @@
#include <linux/tcp.h>
#include <net/tcp.h>

-#ifdef CONFIG_NET_RADIO
+#if defined CONFIG_NET_RADIO || defined CONFIG_WLAN_80211
# include <linux/wireless.h>
#endif
#include "vmnetInt.h"
@@ -764,7 +764,7 @@
{
#ifdef CONFIG_WIRELESS_EXT
return dev->wireless_handlers != NULL;
-#elif !defined(CONFIG_NET_RADIO)
+#elif !defined CONFIG_NET_RADIO && !defined CONFIG_WLAN_80211
return FALSE;
#elif WIRELESS_EXT > 19
return dev->wireless_handlers != NULL;
diff -ubBr vmnet-only.old/filter.c vmnet-only/filter.c
--- vmnet-only.old/filter.c 2007-11-28 19:11:12.000000000 +0900
+++ vmnet-only/filter.c 2008-03-24 22:41:08.000000000 +0900
@@ -12,6 +12,11 @@
#include <linux/ip.h>
#include "compat_skbuff.h"
#include <linux/netdevice.h>
+
+#define NF_IP_LOCAL_OUT NF_INET_LOCAL_OUT
+#define NF_IP_LOCAL_IN NF_INET_LOCAL_IN
+#define NF_IP_POST_ROUTING NF_INET_POST_ROUTING
+
/*
* All this makes sense only if NETFILTER support is configured in our kernel.
*/
diff -ubBr vmnet-only.old/vmnetInt.h vmnet-only/vmnetInt.h
--- vmnet-only.old/vmnetInt.h 2007-11-28 19:25:06.000000000 +0900
+++ vmnet-only/vmnetInt.h 2008-03-16 21:05:28.000000000 +0900
@@ -78,8 +78,10 @@
*/
#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 5, 65)
# define SET_SK_DEAD(_sk, _val) (_sk)->dead = (_val)
-#else
+#elif LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 25)
# define SET_SK_DEAD(_sk, _val) sock_valbool_flag(_sk, SOCK_DEAD, _val)
+#else
+# define SET_SK_DEAD(_sk, _val) sock_set_flag(_sk, SOCK_DEAD)
#endif

I just compiled it on 2.6.25, and it loads fine. But I didn't yet launched a VM.

devsk
Advocate

Joined: 24 Oct 2003
Posts: 2995
Location: Bay Area, CA

Posted: Tue Apr 22, 2008 1:59 am Post subject:

Link31 wrote:

I just compiled it on 2.6.25, and it loads fine. But I didn't yet launched a VM.

did you launch it yet? I would be very much interested in knowing if the virtual machine worked after this patch.

PS: Ok, I tested this and it seems to work so far.

Last edited by devsk on Tue Apr 22, 2008 2:48 am; edited 1 time in total

pal_gene
n00b
n00b

Joined: 15 Nov 2005
Posts: 54

Posted: Tue Apr 22, 2008 2:32 am Post subject:

http://jon.limedaley.com/plog/archives/2008/04/18/vmware-1.0.5-patch-for-2.6.25-kernel i met this site. gentoo has already some patches, so we need some drop from those. _________________ what happen my profile # [i speak "ENGRISH"!]

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Mon Apr 28, 2008 2:42 pm Post subject:

@Link31: i tried your hack, but i am not lucky, so far.
the first patch-patch seems to work, but on the second i get a error.

Code:

xeon vmware-modules # emerge -1 ./vmware-modules-1.0.0.15-r1.ebuild

*** emerging by path is broken and may not always work!!!

Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.15-r1 to /
* vmware-any-any-update115.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking vmware-any-any-update115.tar.gz ;-) ... [ ok ]
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 2.6.25-gentoo-r1-blackbit
>>> Unpacking source...
>>> Unpacking vmware-any-any-update115.tar.gz to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
>>> Unpacking ./vmware-any-any-update115/vmmon.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
* Applying various patches (bugfixes/updates) ...
* 000_all_makefile-include-directory.patch ... [ ok ]
* 020_all_epoll-def-warnings.patch ... [ ok ]
* Done with patching
* Applying various patches (bugfixes/updates) ...
* 030_all_fix-linux-headers.patch ... [ ok ]
* Done with patching
* Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ]
>>> Unpacking ./vmware-any-any-update115/vmnet.tar to /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work
* Applying various patches (bugfixes/updates) ...
* 000_all_makefile-include-directory.patch ... [ ok ]
* 020_all_epoll-def-warnings.patch ... [ ok ]
* Done with patching
* Applying various patches (bugfixes/updates) ...
* 021_all_wireless_fix.patch ...

* Failed Patch: 021_all_wireless_fix.patch !
* ( /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch )
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/temp/021_all_wireless_fix.patch-7713.out

*
* ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 3221: Called vmware-mod_src_unpack
* environment, line 3935: Called epatch 'src_unpack'
* environment, line 1502: Called die
* The specific snippet of code:
* die "Failed Patch: ${patchname}!";
* The die message:
* Failed Patch: 021_all_wireless_fix.patch!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/temp/environment'.
*
xeon vmware-modules #

021_all_wireless_fix.patch-7713.out:

Code:

***** 021_all_wireless_fix.patch *****

======================================

PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch

======================================
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
|--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
|+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/filter.c vmnet-only/filter.c
|--- vmnet-only.old/filter.c 2007-11-28 19:11:12.000000000 +0900
|+++ vmnet-only/filter.c 2008-03-24 22:41:08.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/vmnetInt.h vmnet-only/vmnetInt.h
|--- vmnet-only.old/vmnetInt.h 2007-11-28 19:25:06.000000000 +0900
|+++ vmnet-only/vmnetInt.h 2008-03-16 21:05:28.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
======================================

PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch

======================================
patching file bridge.c
Hunk #2 succeeded at 855 (offset 91 lines).
patching file filter.c
patching file vmnetInt.h
Hunk #1 FAILED at 78.
1 out of 1 hunk FAILED -- saving rejects to file vmnetInt.h.rej
======================================

PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch

======================================
missing header for unified diff at line 4 of patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
|--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
|+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
missing header for unified diff at line 25 of patch
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/filter.c vmnet-only/filter.c
|--- vmnet-only.old/filter.c 2007-11-28 19:11:12.000000000 +0900
|+++ vmnet-only/filter.c 2008-03-24 22:41:08.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 40 of patch
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/vmnetInt.h vmnet-only/vmnetInt.h
|--- vmnet-only.old/vmnetInt.h 2007-11-28 19:25:06.000000000 +0900
|+++ vmnet-only/vmnetInt.h 2008-03-16 21:05:28.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
======================================

PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch

======================================
missing header for unified diff at line 4 of patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
|--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
|+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
missing header for unified diff at line 25 of patch
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/filter.c vmnet-only/filter.c
|--- vmnet-only.old/filter.c 2007-11-28 19:11:12.000000000 +0900
|+++ vmnet-only/filter.c 2008-03-24 22:41:08.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 40 of patch
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/vmnetInt.h vmnet-only/vmnetInt.h
|--- vmnet-only.old/vmnetInt.h 2007-11-28 19:25:06.000000000 +0900
|+++ vmnet-only/vmnetInt.h 2008-03-16 21:05:28.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
======================================

PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/local/blackbit-portage/app-emulation/vmware-modules/files/patches/vmnet/021_all_wireless_fix.patch

======================================
missing header for unified diff at line 4 of patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
|--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
|+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
--------------------------
No file to patch. Skipping patch.
2 out of 2 hunks ignored
missing header for unified diff at line 25 of patch
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/filter.c vmnet-only/filter.c
|--- vmnet-only.old/filter.c 2007-11-28 19:11:12.000000000 +0900
|+++ vmnet-only/filter.c 2008-03-24 22:41:08.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
missing header for unified diff at line 40 of patch
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ubBr vmnet-only.old/vmnetInt.h vmnet-only/vmnetInt.h
|--- vmnet-only.old/vmnetInt.h 2007-11-28 19:25:06.000000000 +0900
|+++ vmnet-only/vmnetInt.h 2008-03-16 21:05:28.000000000 +0900
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored

Link31
Apprentice

Joined: 17 Apr 2006
Posts: 200
Location: France

Posted: Mon Apr 28, 2008 7:57 pm Post subject:

alex.blackbit wrote:

@Link31: i tried your hack, but i am not lucky, so far.
the first patch-patch seems to work, but on the second i get a error.

Code:

xeon vmware-modules # emerge -1 ./vmware-modules-1.0.0.15-r1.ebuild

It works for me with this tarball: http://mirror.ovh.net/gentoo-distfiles/distfiles/vmware-any-any-update115.tar.gz

Just checked it, I have the same offset warning at line 855 but the patch works anyways.

Here is the original patch, without formatting (this forum may have corrupted the patch somehow), bzip2'ed and base64 encoded.

Code:

QlpoOTFBWSZTWeWtkI0AAjrfgGIweX///3+t38C/79/sUAMqb1SFaCglFMpim1PNUeptI8kaehNG
QGmjQaZAANM1BlKGj0TR6gNDRoAAAAAAAACU0iaBNIADRo0AaAANAAGgA4yZNGIYmmAgYE0wRgmJ
ppoAMIJFCZJhKeyE1GmmgZNBp6hoyA0eoZHqaGiUfQUTvLk2O3Le27A/chZPqZnhmVk73KzO6t0x
NXHNYHNmmG5Z6p1CTESQ2gEIK4XEwB2XgPcJmoUFgSpVpJcB4sBhoCJK87SEgTBfDEOQ8t6elxdc
+Kp8c4xKda7ElkVJB9QolRlURVHW0aIa8D26ZvvFAqquG+LfWm9Ig0VIoQTp07s7uzayzTGf2MDP
zD1W2MN+TWyxkAmagI4eUsoWNcUlxNwwWRNNQDhOEt5iJBdr+m+DQbHrtGLWXWuMlQF5fekia8Nt
FmhASSX8UKEEnvgs7A5QYG8cosRbpiM+AxzE5hWojPJQUiUndW2my53OocuEX6ZYBPaHClVM4qok
K4Z5GYeEkRsqciro8QgU0iniiRMw+EogCNVJZCG4VT5PsXAfI40QvXMBAPEFEegNmwLCfUaxZyK3
mtiJEkQDWdLRach7+g/IXkgKLIWxSowOlLMBUiRQtCsJLaeZFhJYlCozlRtKwwvYVEDExKRUwklE
URjJkTriFgXFxEaTPgpKhEGrcHHHEE9bTBFnIlRSfNiVEziZSGs5MGVorZImSDSihWaBaMrf1CRG
LQPEY1LHbkMtAjdl5UZkfNOUS6d1orZghyAadR6on7JsHXmFaK5LbsOpVrW22zJeFxxpmo+iUBQ6
A/EpB0OCE4K0CeQNOYbUxBJzVFaGVYEEQaMJ7gVJHEaCsKakiRl3bgmZTM9DgorsIlFDcEiQX/5V
dvEWgcc1GjDdsIwFcSS6g1wNAWpaUK3FAZMVMChaQSI74K1oxoJU86KBgS1CkI+sE6rjGwrrttHJ
USAyBNSVwYjUjlHxjknLLrYDKk6QBSQ0tzSQoE4LOopX2Xd7uq0Ky8TsBWhwPgMAvQqv2/+LuSKc
KEhy1shGgA==

Decode it with

Code:

cat base64_data | base64 -d -i | bunzip2 > 021_all_wireless_fix.patch.good

I have this ebuild in the overlay, if you think it is relevant (vmware-modules-1.0.0.15-r1.ebuild)

Code:

# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/app-emulation/vmware-modules/vmware-modules-1.0.0.15-r1.ebuild,v 1.4 2007/07/12 06:39:56 mr_bones_ Exp $

KEYWORDS="amd64 x86"
VMWARE_VER="VME_S1B1"

inherit vmware-mod

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Mon Apr 28, 2008 10:00 pm Post subject:

i got the following differences:

Code:

xeon vmnet # diff -u 021_all_wireless_fix.patch 021_all_wireless_fix.patch.good
--- 021_all_wireless_fix.patch 2008-04-28 16:38:00.659522919 +0200
+++ 021_all_wireless_fix.patch.good 2008-04-28 23:48:23.018832037 +0200
@@ -1,6 +1,6 @@
diff -uNr vmnet-only.old/bridge.c vmnet-only/bridge.c
---- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
-+++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
+--- vmnet-only.old/bridge.c 2008-01-06 21:25:04.000000000 +0000
++++ vmnet-only/bridge.c 2008-01-06 21:27:42.000000000 +0000
@@ -32,7 +32,7 @@
#include <linux/tcp.h>
#include <net/tcp.h>
@@ -46,4 +46,4 @@
# define SET_SK_DEAD(_sk, _val) sock_valbool_flag(_sk, SOCK_DEAD, _val)
+#else
+# define SET_SK_DEAD(_sk, _val) sock_set_flag(_sk, SOCK_DEAD)
- #endif
+ #endif
xeon vmnet

vmware works again, now. thanks for the hints!
but one thing is still amazing:

Code:

# emerge -1 ./vmware-modules-1.0.0.15-r1.ebuild|tee log.txt
# grep -E "warning|note" log.txt|wc -l
77
#

i am sure this could be done a little bit better.

Link31
Apprentice

Joined: 17 Apr 2006
Posts: 200
Location: France

Posted: Tue Apr 29, 2008 1:33 am Post subject:

omg a diff of a diff

Very readable

alex.blackbit wrote:

but one thing is still amazing:

Code:

# emerge -1 ./vmware-modules-1.0.0.15-r1.ebuild|tee log.txt
# grep -E "warning|note" log.txt|wc -l
77
#

i am sure this could be done a little bit better.

Sure. But I don't think that most of these warnings are caused by this hack. As far I know, there have been warnings while emerging vmware-modules for a some time. The vmware code and/or the Makefiles are simply not clean and don't always follow the kernel API (voluntarily or not).

Of course we could write a patch to fix that, but the Gentoo policy is to fix such things upstream.

alex.blackbit
Advocate

Joined: 26 Jul 2005
Posts: 2397

Posted: Tue Apr 29, 2008 9:20 am Post subject:

you are right, these things are not caused by the hack.

Display posts from previous:

	Gentoo Forums Forum Index Other Things Gentoo	All times are GMT
Page 1 of 1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy