Bug 232113 – app-emulation/vmware-modules + sys-kernel/gentoo-sources-2.6.26 - vmmon-only/linux/driver.c:171: error: unknown field ‘nopage’ specified in initializer

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Miroslaw Mieszczak 2008-07-17 20:48:48 UTC]

as in summary, please see Actual results

Reproducible: Always

Actual Results:  
>>> 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.26-gentoo
>>> 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[1]: uwaga: serwer zadań niedostępny: używanie -j1.  Należy dodać `+' do nadrzędnej reguły make.

  WARNING: Symbol version dump /usr/src/linux-2.6.26-gentoo/Module.symvers
           is missing; modules will have no dependencies and modversions.

/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:171: error: unknown field ‘nopage’ specified in initializer
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:172: warning: initialization from incompatible pointer type
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:175: error: unknown field ‘nopage’ specified in initializer
/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only/linux/driver.c:176: 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] Błąd 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r1/work/vmmon-only] Błąd 2
make[1]: *** [sub-make] Błąd 2
make: *** [vmmon.ko] Błąd 2
 *
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3279:  Called linux-mod_src_compile
 *             environment, line 2489:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"                                               CC=\"$(get-KERNEL_CC)\"                              LDFLAGS=\"$(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=x86_64-pc-linux-gnu-gcc CC=x86_64-pc-linux-gnu-gcc LDFLAGS=   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.
 * 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'.
 * This ebuild is from an overlay: '/home/portage/local/portage/'
 *

 * Messages for package app-emulation/vmware-modules-1.0.0.15-r1:

 *
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3279:  Called linux-mod_src_compile
 *             environment, line 2489:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"                                               CC=\"$(get-KERNEL_CC)\"                              LDFLAGS=\"$(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=x86_64-pc-linux-gnu-gcc CC=x86_64-pc-linux-gnu-gcc LDFLAGS=   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.
 * 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'.
 * This ebuild is from an overlay: '/home/portage/local/portage/'
 *

[Comment 1 Miroslaw Mieszczak 2008-07-17 20:49:08 UTC]

Created attachment 160664 [details]
emerge --info

[Comment 2 Miroslaw Mieszczak 2008-07-17 20:56:27 UTC]

probably there is solution:

http://communities.vmware.com/thread/150690

I will try it

[Comment 3 Jeroen Roovers (RETIRED) 2008-07-17 21:18:44 UTC]

*** This bug has been marked as a duplicate of bug 227303 ***