1 |
Hello Everyone, |
2 |
|
3 |
I moddified the "CONFIG_UNUSED_SYMBOLS" paramter and when trying to emerge |
4 |
vmware-server I am presented with another error: |
5 |
|
6 |
|
7 |
* |
8 |
* ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed. |
9 |
* Call stack: |
10 |
* ebuild.sh, line 49: Called src_compile |
11 |
* environment, line 3723: Called linux-mod_src_compile |
12 |
* environment, line 2841: Called die |
13 |
* The specific snippet of code: |
14 |
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" |
15 |
CROSS_COMPILE=${CHOST}- |
16 |
LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} |
17 |
${BUILD_PARAMS} ${BUILD_TARGETS} " || die |
18 |
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- |
19 |
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} |
20 |
${BUILD_TARGETS}"; |
21 |
* The die message: |
22 |
* Unable to emake HOSTCC=i686-pc-linux-gnu-gcc |
23 |
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_S1B1 |
24 |
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build |
25 |
* |
26 |
* If you need support, post the topmost build error, and the call stack if |
27 |
relevant. |
28 |
* A complete build log is located at |
29 |
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/build.log'. |
30 |
* The ebuild environment file is located at |
31 |
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'. |
32 |
* |
33 |
|
34 |
>>> Failed to emerge app-emulation/vmware-modules-1.0.0.15-r2, Log file: |
35 |
|
36 |
>>> |
37 |
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/build.log' |
38 |
|
39 |
* Messages for package app-emulation/vmware-modules-1.0.0.15-r2: |
40 |
|
41 |
* |
42 |
* ERROR: app-emulation/vmware-modules-1.0.0.15-r2 failed. |
43 |
* Call stack: |
44 |
* ebuild.sh, line 49: Called src_compile |
45 |
* environment, line 3723: Called linux-mod_src_compile |
46 |
* environment, line 2841: Called die |
47 |
* The specific snippet of code: |
48 |
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" |
49 |
CROSS_COMPILE=${CHOST}- |
50 |
LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} |
51 |
${BUILD_PARAMS} ${BUILD_TARGETS} " || die |
52 |
"Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- |
53 |
LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} |
54 |
${BUILD_TARGETS}"; |
55 |
* The die message: |
56 |
* Unable to emake HOSTCC=i686-pc-linux-gnu-gcc |
57 |
CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= auto-build VMWARE_VER=VME_S1B1 |
58 |
KERNEL_DIR=/usr/src/linux KBUILD_OUTPUT=/lib/modules/2.6.30-gentoo-r5/build |
59 |
* |
60 |
* If you need support, post the topmost build error, and the call stack if |
61 |
relevant. |
62 |
* A complete build log is located at |
63 |
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/build.log'. |
64 |
* The ebuild environment file is located at |
65 |
'/var/tmp/portage/app-emulation/vmware-modules-1.0.0.15-r2/temp/environment'. |
66 |
* |
67 |
|
68 |
Thanks In Advanced, |
69 |
Ninus |