|
楼主 |
发表于 2006-4-7 10:17:43
|
显示全部楼层
[root@tomren vmware-any-any-update99]# perl runme.pl
Updating /usr/bin/vmware-config.pl ... already patched
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.
Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? [yes] y
Making sure services for VMware Workstation are stopped.
Stopping VMware services:
Virtual machine monitor [确定]
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the mime type icons?
[/usr/share/icons]
What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]
In which directory do you want to install the application's icon?
[/usr/share/pixmaps]
Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes] y
Using compiler "/usr/bin/gcc". Use environment variable CC to override.
What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.16-1.2080_FC5/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.16-1.2080_FC5/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.16-1.2080_FC5-x86_64'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
cc1plus: 警告:命令行选项“-Wstrict-prototypes”对 Ada/C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告:命令行选项“-Wdeclaration-after-statement”对 C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告:命令行选项“-Wno-pointer-sign”对 C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告:命令行选项“-Wstrict-prototypes”对 Ada/C/ObjC 是有效的,但对 C++ 无效
cc1plus: 警告:命令行选项“-ffreestanding”对 C/ObjC 是有效的,但对 C++ 无效
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: 警告:此函数中的 ‘sysenterState$validEIP’ 在使用前可能未初始化
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: 警告:此函数中的 ‘sysenterState$cs’ 在使用前可能未初始化
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: 警告:此函数中的 ‘sysenterState$rsp’ 在使用前可能未初始化
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: 警告:此函数中的 ‘sysenterState$rip’ 在使用前可能未初始化
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.16-1.2080_FC5-x86_64'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
The module loads perfectly in the running kernel.
Do you want networking for your virtual machines? (yes/no/help) [no] n
Starting VMware services:
Virtual machine monitor [确定]
The configuration of VMware Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".
Enjoy,
--the VMware team |
|