[gentoo-user] Vmware 1.0.9 emerge problem

[gentoo-user] Vmware 1.0.9 emerge problem

[Nick Khamis]

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

Hello Everyone,

I have a fresh isntall x86 and I am trying to emerge vmware-server 1.0.9,
and I am presented with the follwoing:

 * Checking for suitable kernel configuration options...
 *   CONFIG_UNUSED_SYMBOLS:     is not set when it should be.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * Once you have satisfied these options, please try merging
 * this package again.
 *
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *                           ebuild.sh, line   49:  Called pkg_setup
 *   vmware-modules-1.0.0.15-r2.ebuild, line   17:  Called
vmware-mod_pkg_setup
 *                   vmware-mod.eclass, line   36:  Called
linux-mod_pkg_setup
 *                    linux-mod.eclass, line  578:  Called
linux-info_pkg_setup
 *                   linux-info.eclass, line  752:  Called
check_extra_config
 *                   linux-info.eclass, line  647:  Called die
 * The specific snippet of code:
 *           die "Incorrect kernel configuration options"
 *  The die message:
 *   Incorrect kernel configuration options
 *
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/die.env'.
 *


I have FUSE built into the kernel, is there anything else I am missing?

Regards,
Ninus

[-- Attachment #2: Type: text/html, Size: 1689 bytes --]

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Stefan G. Weichinger]

Nick Khamis schrieb:

>  * Checking for suitable kernel configuration options...
>  *   CONFIG_UNUSED_SYMBOLS:     is not set when it should be.

You have to recompile your kernel after setting the parameter

CONFIG_UNUSED_SYMBOLS=y

with

"make menuconfig" in /usr/src/linux or

"genkernel --menuconfig --no-clean all" ...

It depends on your way of compiling your kernels.

After rebooting into your rebuilt/reconfigured kernel you should be able
to emerge vmware-server.

Stefan

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Nick Khamis]

[-- Attachment #1: Type: text/plain, Size: 209 bytes --]

Hey Stefan,

I figured that much, I am in  ".config - Linux Kernel v2.6.30-gentoo-r5
Configuration" right now and I cannot find CONFIG_UNUSED_SYMBOLS. Where the
hell is this things.

Thanks In Advanced!
Ninus

[-- Attachment #2: Type: text/html, Size: 241 bytes --]

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Xavier Parizet]

Nick Khamis a écrit :
> Hey Stefan,
> 
> I figured that much, I am in  ".config - Linux Kernel v2.6.30-gentoo-r5
> Configuration" right now and I cannot find CONFIG_UNUSED_SYMBOLS. Where
> the hell is this things.

To search for a specific CONFIG_ in the kernel config, on make menuconfig, type
'/' key to search for a key, then after typing UNUSED_SYMBOLS, you'll find it
under Kernel hacking --> [ ] Enable unused/obsolete exported symbols.

HTH.

> Thanks In Advanced!
> Ninus

PS: please stop stripping the mails you answer in your... answers ! This breaks
the conversation. Thanks.

--
Xavier Parizet
YaGB: http://gentooist.com

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Nick Khamis]

[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]

Hello Everyone,

I moddified the "CONFIG_UNUSED_SYMBOLS" paramter and when trying to emerge
vmware-server I am presented with another error:


*
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3723:  Called linux-mod_src_compile
 *             environment, line 2841:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"                         ${BUILD_FIXES}
    ${BUILD_PARAMS}                         ${BUILD_TARGETS} " || die
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}-
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_S1B1
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build
 *
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'.
 *

>>> Failed to emerge app-emulation/vmware-modules-1.0.0.15-r2, Log file:

>>>
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/build.log'

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

 *
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3723:  Called linux-mod_src_compile
 *             environment, line 2841:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"                         ${BUILD_FIXES}
    ${BUILD_PARAMS}                         ${BUILD_TARGETS} " || die
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}-
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_S1B1
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build
 *
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'.
 *

Thanks In Advanced,
Ninus

[-- Attachment #2: Type: text/html, Size: 3261 bytes --]

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Nick Khamis]

[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]

Hello Everyone,

I moddified the "CONFIG_UNUSED_SYMBOLS" paramter and when trying to emerge
vmware-server I am presented with another error:


*
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3723:  Called linux-mod_src_compile
 *             environment, line 2841:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"                         ${BUILD_FIXES}
    ${BUILD_PARAMS}                         ${BUILD_TARGETS} " || die
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}-
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_S1B1
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build
 *
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'.
 *

>>> Failed to emerge app-emulation/vmware-modules-1.0.0.15-r2, Log file:

>>>
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/build.log'

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

 *
 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3723:  Called linux-mod_src_compile
 *             environment, line 2841:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"                         ${BUILD_FIXES}
    ${BUILD_PARAMS}                         ${BUILD_TARGETS} " || die
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}-
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_S1B1
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build
 *
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'.
 *

Thanks In Advanced,
Ninus

[-- Attachment #2: Type: text/html, Size: 3318 bytes --]

Re: [gentoo-user] Vmware 1.0.9 emerge problem

[Nick Khamis]

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

I emerged vmware-modules with no problem but still have a hard time with
vmare-server:

 * ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 3723:  Called linux-mod_src_compile
 *             environment, line 2841:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
        CROSS_COMPILE=${CHOST}-
LDFLAGS=\"$(get_abi_LDFLAGS)\"                         ${BUILD_FIXES}
                    ${BUILD_PARAMS}         ${BUILD_TARGETS} " || die
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}-
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   auto-build VMWARE_VER=VME_S1B1
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build

Regards,
Ninus.

[-- Attachment #2: Type: text/html, Size: 1136 bytes --]