* Running kbuildsycoca to build global database ... [ ok ]
* If you want to use konqueror as a filemanager, install the dolphin kpart:
* emerge -1 kde-base/dolphin:4.3
*
* To use Java on webpages: emerge jre
>>> Regenerating /etc/ld.so.cache...
>>> Recording kde-base/konqueror in "world" favorites file...
* Messages for package dev-java/sun-jdk-1.6.0.17:
* Fallback PaX marking -m
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/appletviewer
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/apt
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/extcheck
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/idlj
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jar
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jarsigner
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/java
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/javac
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/javadoc
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/javah
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/javap
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/javaws
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jconsole
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jdb
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jhat
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jinfo
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jmap
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jps
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jrunscript
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jsadebugd
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jstack
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jstat
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/jstatd
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/keytool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/native2ascii
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/orbd
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/pack200
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/policytool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/rmic
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/rmid
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/rmiregistry
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/schemagen
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/serialver
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/servertool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/tnameserv
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/unpack200
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/wsgen
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/wsimport
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/bin/xjc
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/java
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/java_vm
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/javaws
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/keytool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/orbd
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/pack200
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/policytool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/rmid
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/rmiregistry
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/servertool
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/tnameserv
* /var/tmp/portage/dev-java/sun-jdk-1.6.0.17/work/jdk1.6.0_17/jre/bin/unpack200
* A revdep-rebuild control file was installed to prevent reinstalls due to
* missing dependencies (see bug #177925 for more info). Note that some parts
* of the JVM may require dependencies that are pulled only through respective
* USE flags (typically X, alsa, odbc) and some Java code may fail without them.
*
* This version finally brings a browser plugin for amd64
* It is the so-called Next-Generation Plug-In (plugin2)
* Use eselect java-nsplugin to select it (sun-jdk-1.6).
* Note that it works only in Firefox 3 or newer browsers!
* For more info see https://jdk6.dev.java.net/plugin2/
Now we have only one available jave plugin
*
* Please reinstall eclipse-sdk if you have it installed and want
* workaround for bug #215150.
* Messages for package app-crypt/pinentry-0.7.5:
* We no longer install pinentry-curses and pinentry-qt SUID root by default.
* Linux kernels >=2.6.9 support memory locking for unprivileged processes.
* The soft resource limit for memory locking specifies the limit an
* unprivileged process may lock into memory. You can also use POSIX
* capabilities to allow pinentry to lock memory. To do so activate the caps
* USE flag and add the CAP_IPC_LOCK capability to the permitted set of
* your users.
* Messages for package media-libs/libmodplug-0.8.7:
* Since version 0.8.4 onward, libmodplug supports MIDI playback.
* unfortunately to work correctly, this needs timidity patches,
* but the code does not support the needed 'source' directive to
* work with the patches currently in portage. For this reason it
* will not work as intended yet.
* Messages for package net-fs/samba-3.0.37:
* It is possible to start/stop daemons separately:
* Create a symlink from /etc/init.d/samba.{smbd,nmbd,winbind} to
* /etc/init.d/samba. Calling /etc/init.d/samba directly will start
* the daemons configured in /etc/conf.d/samba
* The mount/umount.cifs helper applications are not included anymore.
* Please install net-fs/mount-cifs instead.
* If you're upgrading from 3.0.24 or earlier, please make sure to
* restart your clients to clear any cached information about the server.
* Otherwise they might not be able to connect to the volumes.
* Messages for package app-crypt/gnupg-2.0.11:
* If you wish to view images emerge:
* media-gfx/xloadimage, media-gfx/xli or any other viewer
* Remember to use photo-viewer option in configuration file to activate
* the right viewer
* Messages for package x11-libs/qt-core-4.5.3-r2:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-script-4.5.3-r1:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-test-4.5.3-r1:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-sql-4.5.3:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-dbus-4.5.3-r1:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-gui-4.5.3-r2:
* If you get the following error when setting Qt to use the GTK style:
* "QGtkStyle cannot be used together with the GTK_Qt engine."
* make sure you have GTK configured to NOT use the GTK_Qt engine and
* export GTK2_RC_FILES="$HOME/.gtkrc-2.0" in your environment.
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-qt3support-4.5.3:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-svg-4.5.3-r1:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package x11-libs/qt-opengl-4.5.3-r1:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package kde-base/oxygen-icons-4.3.1:
* QA Notice:
* Package oxygen-icons is breaking /usr/share/config permissions.
* Please report this issue to gentoo bugzilla.
* Messages for package x11-libs/qt-webkit-4.5.3:
* After a rebuild or upgrade of Qt, it can happen that Qt plugins (such as Qt
* and KDE styles and widgets) can no longer be loaded. In this situation you
* should recompile the packages providing these plugins. Also, make sure you
* compile the Qt packages, and the packages that depend on it, with the same
* GCC version and the same USE flag settings (especially the debug flag).
*
* Packages that typically need to be recompiled are kdelibs from KDE4, any
* additional KDE4/Qt4 styles, qscintilla and PyQt4. Before filing a bug report,
* make sure all your Qt4 packages are up-to-date and built with the same
* configuration.
*
* For more information, see
* Messages for package kde-base/kdelibs-4.3.1-r2:
* Your homedir is set to ${HOME}/.kde4
*
* If you experience weird application behavior (missing texts, etc.) run as root:
* # chmod 755 -R /usr/share/config
* Messages for package kde-base/kdebase-kioslaves-4.3.1:
* Note that if you upgrade strigi, you have to rebuild this package.
* Messages for package kde-base/konqueror-4.3.1:
* If you want to use konqueror as a filemanager, install the dolphin kpart:
* emerge -1 kde-base/dolphin:4.3
*
* To use Java on webpages: emerge jre
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* Regenerating GNU info directory index...
* Processed 164 info files.
* IMPORTANT: 1 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
When install vmware-workstation
* Updating desktop mime database ...
* Updating icons cache ... [ ok ]
* Before you can use vmware-workstation, you must configure a default network setup.
* You can do this by running 'emerge --config vmware-workstation'.
>>> Recording app-emulation/vmware-workstation in "world" favorites file...
* Messages for package app-emulation/vmware-workstation-6.5.3.185404:
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / ` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/applications/vmware-player.desktop
* /usr/share/applications/vmware-workstation.desktop
* /usr/share/icons/hicolor/24x24/apps/vmware-acevm.png
* /usr/share/icons/hicolor/24x24/apps/vmware-player.png
* /usr/share/icons/hicolor/24x24/apps/vmware-workstation.png
* /usr/share/icons/hicolor/24x24/mimetypes/application-x-vmware-vm-clone.png
* /usr/share/icons/hicolor/24x24/mimetypes/application-x-vmware-vm.png
* /usr/share/icons/hicolor/16x16/mimetypes/application-x-vmware-vm.png
* /usr/share/icons/hicolor/16x16/mimetypes/application-x-vmware-vm-legacy.png
* /usr/share/icons/hicolor/16x16/mimetypes/application-x-vmware-team.png
* /usr/share/icons/hicolor/16x16/mimetypes/application-x-vmware-vm-clone.png
* /usr/share/icons/hicolor/16x16/apps/vmware-acevm.png
* /usr/share/icons/hicolor/16x16/apps/vmware-player.png
* /usr/share/icons/hicolor/16x16/apps/vmware-workstation.png
* /usr/share/icons/hicolor/48x48/apps/vmware-acevm.png
* /usr/share/icons/hicolor/48x48/apps/vmware-player.png
* /usr/share/icons/hicolor/48x48/apps/vmware-workstation.png
* /usr/share/icons/hicolor/48x48/mimetypes/application-x-vmware-snapshot.png
* /usr/share/icons/hicolor/48x48/mimetypes/application-x-vmware-vmfoundry.png
* /usr/share/icons/hicolor/48x48/mimetypes/application-x-vmware-vmdisk.png
* /usr/share/icons/hicolor/48x48/mimetypes/application-x-vmware-vm.png
* /usr/share/icons/hicolor/48x48/mimetypes/application-x-vmware-team.png
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-vm-legacy.svg
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-vm.svg
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-snapshot.svg
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-vmfoundry.svg
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-vm-clone.svg
* /usr/share/icons/hicolor/scalable/mimetypes/application-x-vmware-team.svg
* /usr/share/icons/hicolor/scalable/apps/vmware-acevm.svg
* /usr/share/icons/hicolor/scalable/apps/vmware-player.svg
* /usr/share/icons/hicolor/scalable/apps/vmware-workstation.svg
* /usr/share/icons/hicolor/32x32/apps/vmware-player.png
* /usr/share/icons/hicolor/32x32/apps/vmware-workstation.png
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'app-emulation/vmware-workstation-6.5.3.185404' merged despite
* file collisions. If necessary, refer to your elog messages for the
* whole content of the above message.
* Before you can use vmware-workstation, you must configure a default network setup.
* You can do this by running 'emerge --config vmware-workstation'.
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
* IMPORTANT: 1 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
emerge --config vmware-workstation
Configuring pkg...
Network settings database seems to be invalid,configuring default settings
Configuring Bridged network vmnet0
Configuring hostonly network vmnet1, probing for unused subnet ...
Configuring NAT network vmnet8, probing for unused subnet ...
Configured default networks - Bridged, Hostonly, NAT
/usr/bin/vmware-config.pl
The following VMware kernel modules have been found on your system that were
not installed by the VMware Installer. Please remove them then run this
installer again.
vmnet
vmmon
vmci
vmblock
Execution aborted.
modprobe -r vmnet vmmon vmci vmblock #useless
rm /lib64/modules/2.6.30-gentoo-r4/misc/vmnet.ko
rm ..................................../vmmon.ko
rm ..................................../vmci.ko
rm ..................................../vmblock.ko
OK. Now begin to /usr/bin/vmware-config.pl
不过还是出错了，原因是受之前安装的其它版本的影响
于是，
先将安装的vmware卸载，
emerge -C vmware-workstation vmware-modules
下面将以前安装的vmware用
/usr/bin/vmware-uninstall.pl
清除。
再将重新emerge -av vmware-workstation
But I can find serial number of 6.5.3.
I have to transfer to 6.0.5
I have an available S/N of that version.
So I change the kernel from 2.6.30 down to 2.6.25 to fit the requirement of vmware-workstation.
After recompile the kernel 2.6.25-r9. I try to reinstall the vmware-workstation-6.0.5.109488.
Now, another problem come out. A error occured whtn try to emerge vmware-workstation.
I have to recompile the package gtkmm and its dependent package including glib, gtk+ etc.
OK，现在五笔输入法装好了，用的是fcitx，不过可能是由于设计这个输入法面向的x86用户，所以在我的amd64机器上安装还需要，用ACCETP_KEYWORDS="~amd64"。
现在安装gtkmm仍旧没有完成。
从现在开始，没有特殊原因，我决定不再升级内核了，好不容易找到一个可以和vmware-workstation匹配的版本。
不过，我现在用的内核本身可能有些问题，在现在有效的一系列内核中，它的名字是暗色的。
计划接下来要升级的软件包为：还没想好，需要再说吧。
阅读(584) | 评论(0) | 转发(0) |
