1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Ronan Klyne wrote: |
5 |
> Sorry - that was unclear. Portage had installed new kernel sources, and |
6 |
> I hadn't built a kernel from them. I initially thought that I could use |
7 |
> the existing kernel, but the vmware-config script would hang. |
8 |
> |
9 |
|
10 |
Ronan, is it possible that you have the "symlink" USE flag set? (If |
11 |
you're not sure about that please post the output of 'emerge -pv |
12 |
gentoo-sources' here) That USE flag changes the /usr/src/linux |
13 |
symlink every time you emerge a new version of the kernel sources. |
14 |
Many ebuilds (like vmware) depend on /usr/src/linux pointing to the |
15 |
(configured) sources of the kernel currently running, sy in most |
16 |
cases it is not a good idea to enable "symlink". |
17 |
|
18 |
> Vladimir G. Ivanovic wrote: |
19 |
> When I run vmware-config.pl, I get the following error: |
20 |
> |
21 |
> Building for VMware Workstation 5.5.x. |
22 |
> Using 2.6.x kernel build system. |
23 |
> make: Entering directory `/tmp/vmware-config0/vmmon-only' |
24 |
> Makefile:127: *** Inappropriate build environment: you wanted to |
25 |
> use gcc version while kernel attempts to use gcc version 4.1.1. |
26 |
> Makefile:129: *** For proper build you'll have to |
27 |
> replace /usr/bin/gcc with symbolic link to . Stop. |
28 |
> make: Leaving directory `/tmp/vmware-config0/vmmon-only' |
29 |
> Unable to build the vmmon module. |
30 |
|
31 |
This is mostly a wild guess from my side, but I think the trouble he |
32 |
is more with the gcc version than vmware itself. Can you please post |
33 |
the output of: |
34 |
'/usr/bin/gcc --version' |
35 |
'gcc-config -l' |
36 |
|
37 |
-----BEGIN PGP SIGNATURE----- |
38 |
Version: GnuPG v1.4.4 (GNU/Linux) |
39 |
|
40 |
iD8DBQFExQzQ6q4f+IV6B/wRAoljAJ43uLNXtF5EDlNhCBT/R0JqBPGWAwCfcNzk |
41 |
tnjWUopYHwRpO/oDo/i6npk= |
42 |
=qLBq |
43 |
-----END PGP SIGNATURE----- |
44 |
-- |
45 |
gentoo-amd64@g.o mailing list |