From: Nick Khamis <symack@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Vmware 1.0.9 emerge problem
Date: Fri, 4 Sep 2009 23:17:10 +0000 [thread overview]
Message-ID: <46d08bd30909041617t1c58b20cy5be27e07831ec90e@mail.gmail.com> (raw)
In-Reply-To: <4AA19B08.2040509@gentooist.com>
[-- 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 --]
next prev parent reply other threads:[~2009-09-04 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 21:00 [gentoo-user] Vmware 1.0.9 emerge problem Nick Khamis
2009-09-04 21:20 ` Stefan G. Weichinger
2009-09-04 22:39 ` Nick Khamis
2009-09-04 22:56 ` Xavier Parizet
2009-09-04 23:17 ` Nick Khamis [this message]
2009-09-04 23:18 ` Nick Khamis
2009-09-04 23:35 ` Nick Khamis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46d08bd30909041617t1c58b20cy5be27e07831ec90e@mail.gmail.com \
--to=symack@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox