vmware-modules-1.0.0.15 worked fine for 2.6.19-rc1, but -r1 fails. * 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.19-rc1-r1' 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/hostif.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 "-Wstrict-prototypes" 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 C/ObjC but not for C++ cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++ include/linux/stddef.h:16: error: expected identifier before 'false' include/linux/stddef.h:16: error: expected `}' before 'false' include/linux/stddef.h:16: error: expected unqualified-id before 'false' include/linux/types.h:36: error: expected initializer before 'bool' /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/common/task.c:43: error: expected declaration before '}' token
Thanks for the report. Unfortunately we're probably going to have to wait for either vmware or the people who produce the generic module sets that we use to release a new version, so it may be several 2.6.19-rcs down the line. Out of interest, have you tried 2.6.19-rc2 with it yet? Please give that a go once an ebuild becomes available and let us know the results, quite often bugs do get into -rc1 releases and vanish again by -rc2. Thanks... 5:)
That's what I figured. I did just try rc2 and it fails in the same manner. Guess I'll just have to wait.
Same problem with vmware-modules-1.0.0.13-r1. Should I start another bug report ?
Nope. One report is fine if it is the same problem.
vanilla-sources 2.6.19-rc3 also has this bug.
A nasty hack is ... 1) To comment the following lines in <linux/stddef.h> // //enum { // false = 0, // true = 1 //}; // 2) To comment the following line in <linux/types.h> //typedef _Bool bool; 3) And to add the 3 following lines to "vmnet-only/userif.c" & "vmnet-only/bridge.c" #ifndef CHECKSUM_HW #define CHECKSUM_HW CHECKSUM_PARTIAL #endif ... well, not elegant but works for me.
(In reply to comment #6) Oups ... I have forgotten point 0). Add a dummy file <linux/config.h> (touch).
Ok, thanks for that, I'll try and look into this sometime this weekend, but I'm a bit snowed under at the moment, so forgive me if it takes a little while...
I'm having the same problem, with 2.6.18-mm3 Francois, how did you get your hack #3 into your system? my emerge always overwrites the mentioned .c files with the ones from the all-updates-package... Here's my emerge-info: Portage 2.1.1-r1 (default-linux/amd64/2006.1/server, gcc-4.1.1, glibc-2.4-r3, 2.6.18-mm3 x86_64) ================================================================= System uname: 2.6.18-mm3 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz Gentoo Base System version 1.12.1 Last Sync: Sat, 28 Oct 2006 07:30:02 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://pandemonium.tiscali.de/pub/gentoo/ http://pandemonium.tiscali.de/pub/gentoo/ http://ftp.club-internet.fr/pub/mirrors/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 apache2 apm berkdb bitmap-fonts cli cracklib crypt cups dlloader dri elibc_glibc fortran gdbm gpm iconv input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog kernel_linux ldap libg++ mailwrapper mono mp3 mysql ncurses nls nptl nptlonly pam pcre perl ppds pppd python readline reflection samba session snmp spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i810 video_cards_mga video_cards_neomagic video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo xml xorg zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #9) > I'm having the same problem, with 2.6.18-mm3 > > Francois, how did you get your hack #3 into your system? my emerge always > overwrites the mentioned .c files with the ones from the all-updates-package... Just my usual trick to fix any kind of problem with unfriendly packages ... After an unsuccessful attempt to compile a package, I edit sources files directly in /var/tmp/portage/... & I restart compilation by issuing the following command to build a binary package. #ebuild usr/portage/app-emulation/vmware-modules/vmware-modules-1.0.0.13-r1.ebuild package (If compilation crash again after "Compilation complete.", don't panic. Do it twice - the second time it will work) and finally emerge your binary package with : #emerge -K --one-shot =app-emulation/vmware-modules-1.0.0.13-r1 It also possible to fetch et edit sources in directly your DISTDIR directory but prior to emerging it as usual you will need to "ebuild <packagename.ebuild> digest" to fix checksums. Don't forget to restore modified files in your /usr/src/linux/include/linux directory thereafter. Good luck!
(In reply to comment #6) > A nasty hack is ... The hack is automated in the script below. Had to do it more than once in last month, hence a script. Remember that its still a hack! #!/bin/bash # once the build for vmare-modules fails, run this tool cd /usr/src/linux cp ./include/linux/stddef.h ./include/linux/stddef.h.orig cp ./include/linux/types.h ./include/linux/types.h.orig sed -i -e "s:typedef _Bool:\/\/typedef _Bool:g" ./include/linux/types.h sed -i -e "/enum {/,/};/d" ./include/linux/stddef.h cd /var/tmp/portage/app-emulation/vmware-modules-*/work/vmnet-only sed -i -e "s:CHECKSUM_HW:CHECKSUM_PARTIAL:g" *.c make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux cd /var/tmp/portage/app-emulation/vmware-modules-*/work/vmmon-only make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux cd /var/tmp/portage/app-emulation/vmware-modules-*/work/ mkdir /lib/modules/`uname -r`/misc/ for i in `find . -name "*.ko"`;do cp $i /lib/modules/`uname -r`/misc/;done depmod -a cd /usr/src/linux cp ./include/linux/stddef.h.orig ./include/linux/stddef.h cp ./include/linux/types.h.orig ./include/linux/types.h ---------------------------------- make sure to cut paste it correctly.
Created attachment 101107 [details] temporary hack to build vmware modules with newer kernels cut & paste will be a problem from the comment, so attaching a file.
Just to confirm same problem on vanilla-sources 2.6.19-rc4
(In reply to comment #13) > Just to confirm same problem on vanilla-sources 2.6.19-rc4 > The attached script doesn't seem to work. Using mm-sources-2.6.19_rc4 The error is: 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.19-rc4-mm2' CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.c:9: include/linux/kernel.h:161: error: expected
(In reply to comment #13) > Just to confirm same problem on vanilla-sources 2.6.19-rc4 > The attached script doesn't seem to work. Using mm-sources-2.6.19_rc4 The error is: 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.19-rc4-mm2' CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.c:9: include/linux/kernel.h:161: error: expected =, ,, ;, asm or __attribute__ before printk_timed_ratelimit make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only/driver.o] Error 1 make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmnet-only] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc4-mm2' make: *** [vmnet.ko] Error 2 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.19-rc4-mm2' CC [M] /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:15: include/linux/kernel.h:161: error: expected =, ,, ;, asm or __attribute__ before printk_timed_ratelimit In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.h:20, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:53: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.h:20, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:53: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:60: error: conflicting types for poll_initwait include/linux/poll.h:62: error: previous declaration of poll_initwait was here /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:160: warning: initialization from incompatible pointer type /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:164: warning: initialization from incompatible pointer type make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.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]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc4-mm2' make: *** [vmmon.ko] Error 2
(In reply to comment #14) > (In reply to comment #13) > > Just to confirm same problem on vanilla-sources 2.6.19-rc4 > > > > The attached script doesn't seem to work. Using mm-sources-2.6.19_rc4 Try to apply my guidelines in comments #6, #7 and #10. It should work for mm-sources. My trick is working fine for vanilla-sources-2.6.19-rc3/rc4.
Thanks, however I am still getting errors (followed #6, #7 and #10): 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.19-rc4-mm2' 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 In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.h:20, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:53: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:16: include/linux/kernel.h:161: error: expected
Thanks, however I am still getting errors (followed #6, #7 and #10): 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.19-rc4-mm2' 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 In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.h:20, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:53: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:16: include/linux/kernel.h:161: error: expected =, ,, ;, asm or __attribute__ before printk_timed_ratelimit In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.h:21, from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:54: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_wait.h:60: error: conflicting types for poll_initwait include/linux/poll.h:62: error: previous declaration of poll_initwait was here /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:160: warning: initialization from incompatible pointer type /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:164: warning: initialization from incompatible pointer type make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.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]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc4-mm2' make: *** [vmmon.ko] Error 2 !!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed. Call stack: ebuild.sh, line 1568: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1261: Called linux-mod_src_compile linux-mod.eclass, line 482: Called die !!! Unable to make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux. !!! If you need support, post the topmost build error, and the call stack if relevant.
An update of the dirty hack to having vmware working with kernel 2.6.19-*. Works with vanilla -rc3, -rc4, -rc5 and should work now with -mm2. 0) Create a dummy file <linux/config.h> 1) Comment the following lines in <linux/stddef.h> //enum { // false = 0, // true = 1 //}; 2) Comment the following line in <linux/types.h> //typedef _Bool bool; 3) (FOR -RC5 & -MM2 ONLY) Comment the following lines in <linux/kernel.h> //extern bool printk_timed_ratelimit(unsigned long *caller_jiffies, // unsigned int interval_msec); 4) Emerge vmware-modules. The compilation will crash. 5) Add the 3 following lines to "vmnet-only/userif.c" & "vmnet-only/bridge.c". Files are in /var/tmp/portage/... #ifndef CHECKSUM_HW #define CHECKSUM_HW CHECKSUM_PARTIAL #endif 6) ebuild /usr/portage/app-emulation/vmware-module/{yourversion}.ebuild package 7) For an unknown reason if step 5 crash, do it again. It will works the second time. 8) emerge --one-shot -K vmware-modules 9) And finally (to avoid problem) undo step #1, #2, #3.
Created attachment 101803 [details] temp script hack for vanilla 2.6.19-rc5 updated installing hack script for vanilla 2.6.19-rc5
Created attachment 101805 [details] temp script hack for vanilla 2.6.19-rc5 fixed opps in last patch
(In reply to comment #19) > Created an attachment (id=101805) [edit] > temp script hack for vanilla 2.6.19-rc5 > > fixed opps in last patch > The hack works fine in compiling the modules (kernel-2.6.19-rc5-mm1) (haven't tested vmware itself though). One thing I had to change though is not /var/tmp/portage/vmware-modules-* but /var/tmp/portage/app-emulation/vmware-modules-* is the correct directory. I don't know which portage version changed that, but I'm running 2.1.2_rc1-r6 Thanks again.
Created attachment 101890 [details] temp script hack for 2.6.19-rc5 fixed the hack for 2 versions of portage ....hmmm maybe I should stop wasting time fixing a hack script and make a patch
Tyler, if you do come up with a patch that affects only the vmware-modules install code (rather than the kernel source which isn't in our control) I'd be very happy to apply it to the code and close the bug. Unfortunately you'll have to make sure that it only triggers if/when the kernel it's built against is >= 2.6.19, because if it only fixes the problem for 2.6.19 but breaks older kernels in the process, we're not going to be able to apply it (since the installed kernel version, isn't necessarily the same as the kernel version being compiled against). That'll mean a fair few ifdefs in the code. I'm still waiting on vmware-any-any-105 to come out and hopefully fix the 2.6.19 problems, but until that happens, or a good patch is written, I'm afraid the ebuild's going to have to stay the same. Sorry for the delay... 5:(
Well, unsure if this will help or not, but I've noticed that vmware-any-any-105update.tar.gz can be found such as on http://platan.vc.cvut.cz/ftp/pub/vmware/.
Sorry, vmware-any-any-update105.tar.gz.
Using update105, vmware compiles and works fine on 2.6.19-rc5-mm1. The only problem is a sandbox violation.
Perfect, thanks for the spot (looks like I checked at it a day too early). I'm away all day today, but I'll try and get to it this evening, or failing that tomorrow. It'll go into the vmware overlay for testing first, but we should get a new version into the tree by the weekend or next week hopefully...
Darkstalker, I've checked this update into the vmware overlay, could you please try that out and report back further details of the sandbox violation? Thanks... 5:)
(In reply to comment #27) > Darkstalker, I've checked this update into the vmware overlay, could you please > try that out and report back further details of the sandbox violation? > Thanks... 5:) > using vmware overlay... here is some details of my sandbox violations. need anything else? with sandbox http://www.ecl.udel.edu/~mcgee/logs/vmware_fail.txt without sandbox http://www.ecl.udel.edu/~mcgee/logs/vmware_success.txt
Nope, that's perfect thanks. Confusing (really, really confusing), but perfect. I'll try and look into it this evening and hopefully figure something out for the weekend... 5:)
Created attachment 102049 [details] compilation try under 2.6.19-rc5-mm2 (amd64) Hello, I didn't success in compiling it from the overlay.
Ok, I'm afraid this is now a much larger problem. It seems no external modules will build with the sandbox in-place with kernels > 2.6.18. Please see bug 149307 for more information. As such, since there have been no other issues with vmware-any-any105, I'll probably end up committing this pretty soon...
It seems I'm having a problem to compile vmware-modules a little different from the other reported in this thread, and the patches posted didn't worked at all. The ollowing shows what I get: >>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.15-r1 to / --10:16:45-- ftp://ftp.las.ic.unicamp.br/pub/gentoo/distfiles/vmware-any-any-update104.tar.gz => `/usr/portage/distfiles/vmware-any-any-update104.tar.gz' Resolving ftp.las.ic.unicamp.br... 143.106.60.116 Connecting to ftp.las.ic.unicamp.br|143.106.60.116|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/gentoo/distfiles ... done. ==> PASV ... done. ==> RETR vmware-any-any-update104.tar.gz ... done. Length: 297,243 (290K) (unauthoritative) 100%[=================================================================================================>] 297,243 52.73K/s ETA 00:00 10:16:51 (52.64 KB/s) - `/usr/portage/distfiles/vmware-any-any-update104.tar.gz' saved [297243] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.19-rc5-mm2 * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * 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.19-rc5-mm2' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o In file included from /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:85: /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'compat_exit' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'exit_code' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to 'int' in declaration of '_syscall1' make[3]: *** [/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o] Error 1 make[2]: *** [_module_/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc5-mm2' make: *** [vmmon.ko] Error 2 !!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called linux-mod_src_compile linux-mod.eclass, line 510: Called die !!! Unable to make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux. !!! If you need support, post the topmost build error, and the call stack if relevant. Should I open a new bug report or anyone knows how I solve it?
Ok, I've pushed vmware-any-any105 out to the tree (give it a couple of hours to synchronize, then emerge --sync) and there's a fix for the sandbox issues in gentoo-sources. I haven't bumped the version number, but do please try recompiling it against your kernel version and post back here if you're still having problems. Rafael, could you please try this too, even though your errors look different? Thanks... 5:)
I'm running the same kernel as Rafael, results with the new ebuild seem the same as his results from before: >>> Downloading 'http://ftp.cvut.cz/vmware/vmware-any-any-update105.tar.gz' --08:46:08-- http://ftp.cvut.cz/vmware/vmware-any-any-update105.tar.gz => `/usr/portage/distfiles/vmware-any-any-update105.tar.gz' Resolving ftp.cvut.cz... 147.32.160.17 Connecting to ftp.cvut.cz|147.32.160.17|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 296,970 (290K) [application/x-tar] 100%[====================================>] 296,970 133.18K/s 08:46:12 (132.96 KB/s) - `/usr/portage/distfiles/vmware-any-any-update105.tar.gz' saved [296970/296970] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking vmware-any-any-update105.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.19-rc5-mm2 >>> Unpacking source... >>> Unpacking vmware-any-any-update105.tar.gz to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work >>> Unpacking ./vmware-any-any-update105/vmmon.tar to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ]>>> Unpacking ./vmware-any-any-update105/vmnet.tar to /var/tmp/portage/vmware-modules-1.0.0.15-r1/work * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ]>>> Source unpacked. >>> Compiling source in /var/tmp/portage/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.19-rc5-mm2' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o In file included from /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:85: /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'compat_exit' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'exit_code' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to 'int' in declaration of '_syscall1' make[3]: *** [/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o] Error 1 make[2]: *** [_module_/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc5-mm2' make: *** [vmmon.ko] Error 2 !!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called linux-mod_src_compile linux-mod.eclass, line 510: Called die !!! Unable to make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux. !!! If you need support, post the topmost build error, and the call stack if relevant. Anything you want me to try?
I found a solution ;-) change export ANY_ANY="vmware-any-any-update104" by export ANY_ANY="vmware-any-any-update105" in file /usr/portage/eclass/vmware.eclass recalculate digest with ebuild /usr/portage/app-emulation/vmware-modules/vmware-modules-1.0.0.15-r1.ebuild digest and recompile :-)
I still fails here, as FEATURES="-sandbox -usersandbox" emerge vmware-player gives: 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.19-rc5-mm2' 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 In file included from /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:85: /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'compat_exit' /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'exit_code' /var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to 'int' in declaration of '_syscall1' make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.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]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc5-mm2' make: *** [vmmon.ko] Error 2 !!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed. Call stack: ebuild.sh, line 1568: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1261: Called linux-mod_src_compile linux-mod.eclass, line 510: Called die !!! Unable to make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux. !!! If you need support, post the topmost build error, and the call stack if relevant.
I compiled the vmware-modules today against a 2.6.19 vanilla kernel and it worked fine, beside the sandbox problem. So I had to copy the modules manualy to the /lib/modules/2.6.19/extra directory. It's no problem to get them loaded into the kernel and vmware-workstation runs fine. >>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-app-emulation_-_vmware-modules-1.0.0.15-r1-9815.log" open_wr: /usr/src/linux-2.6.19/astest9941.out open_wr: /usr/src/linux-2.6.19/astest9945.out open_wr: /usr/src/linux-2.6.19/astest9952.out open_wr: /usr/src/linux-2.6.19/astest9956.out open_wr: /usr/src/linux-2.6.19/astest10184.out open_wr: /usr/src/linux-2.6.19/astest10188.out open_wr: /usr/src/linux-2.6.19/astest10195.out open_wr: /usr/src/linux-2.6.19/astest10199.out --------------------------------------------------------------------------------
(In reply to comment #37) > I compiled the vmware-modules today against a 2.6.19 vanilla kernel and it > worked fine, beside the sandbox problem. The sandbox problem vs kernel 2.6.19 is not unique to vmware-modules. I got the same problem with net-dialup/slmodem package recently.
As requested I've tried to emerge vmware-modules again, but get the same error: >>> Emerging (1 of 1) app-emulation/vmware-modules-1.0.0.15-r1 to / --13:46:20-- http://distfiles.gentoo.org/distfiles/vmware-any-any-update105.tar.gz => `/usr/portage/distfiles/vmware-any-any-update105.tar.gz' Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 64.50.236.52, ... Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 296,970 (290K) [application/x-gzip] 100%[=================================================================================================>] 296,970 131.10K/s 13:46:23 (130.70 KB/s) - `/usr/portage/distfiles/vmware-any-any-update105.tar.gz' saved [296970/296970] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.19-rc6-mm2 * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmmon-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * Applying various patches (bugfixes/updates) ... * 000_all_makefile-include-directory.patch ... [ ok ] * Done with patching * Converting vmnet-only/Makefile to use M= instead of SUBDIRS= ... [ ok ] * 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.19-rc6-mm2' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o In file included from /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:85: /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'compat_exit' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or '...' before 'exit_code' /var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to 'int' in declaration of '_syscall1' make[3]: *** [/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o] Error 1 make[2]: *** [_module_/var/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc6-mm2' make: *** [vmmon.ko] Error 2 !!! ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile ebuild.sh, line 1255: Called linux-mod_src_compile linux-mod.eclass, line 510: Called die !!! Unable to make auto-build VMWARE_VER=VME_S1B1 KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux. !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/portage/local/layman/vmware' Just notice that I'm using the vmware overlay now, and upgraded my kernel to the latest mm-sources (2.6.19-rc6-mm2).
On AMD64 with 2.6.19-rc6-mm2, I receive another strange error: * 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.19-rc6-mm2' make[1]: Warnung: Kein Jobserver verf
On AMD64 with 2.6.19-rc6-mm2, I receive another strange error: * 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.19-rc6-mm2' make[1]: Warnung: Kein Jobserver verfügbar: -j1 wird gesetzt. »+« zur Ursprungsregel hinzufügen. CC [M] /tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o In file included from /tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:85: /tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: Fehler: expected declaration specifiers or »...« before »compat_exit« /tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: Fehler: expected declaration specifiers or »...« before »exit_code« /tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/./include/compat_kernel.h:21: Warnung: »int« ist Standardtyp in Deklaration von »_syscall1« make[3]: *** [/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.o] Fehler 1 make[2]: *** [_module_/tmp/portage/vmware-modules-1.0.0.15-r1/work/vmmon-only] Fehler 2 make[1]: *** [modules] Fehler 2 make[1]: Leaving directory `/usr/src/linux-2.6.19-rc6-mm2' make: *** [vmmon.ko] Fehler 2 Any suggestions? The proposed patches do not work. Cheers, Florian
Guys, everyone who's still getting errors is using the -mm sources, and unfortunately we can't really support every kernel out there. I'll keep an eye out for any patches that might be available for it, but otherwise there isn't a lot I can do. If someone else can figure out the problem and produces patches I'll be happy to test them and if they're stable add them to the package, but otherwise we can't really help with this issue. Sorry... 5:( As such, I'm going to mark this bug as fixed (since it's about the vanilla/gentoo-sources). Could someone suffering from the -mm sources problem please open another bug and reference this one?
I created a new report for the error with mm-sources. http://bugs.gentoo.org/show_bug.cgi?id=157307 thank you all