View previous topic :: View next topic |
Author |
Message |
haneulso Apprentice
Joined: 31 Aug 2004 Posts: 173
|
Posted: Wed Dec 03, 2008 11:39 am Post subject: ati-drivers-8.552-r2 install error |
|
|
I tried to upgrade ati-drivers to 8.552-r2.
But, when I installed, I have a error as below.
Code: |
....
usr/lib64/xorg/modules/esut.a
* QA Notice: The following files contain executable stacks
* Files with executable stacks will not work properly (or at all!)
* on some architectures/operating systems. A bug should be filed
* at http://bugs.gentoo.org/ to make sure the file is fixed.
* For more information, see http://hardened.gentoo.org/gnu-stack.xml
* Please include this file in your report:
* /var/tmp/portage/x11-drivers/ati-drivers-8.552-r2/temp/scanelf-execstack.log
* --- --- RWX usr/lib32/opengl/ati/lib/libGL.so.1.2
* QA Notice: The following shared libraries lack a SONAME
* /var/tmp/portage/x11-drivers/ati-drivers-8.552-r2/image/usr/lib64/libatiadlxx.so
making executable: usr/lib64/libfglrx_gamma.so.1.0
* checking 133 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). Add "collision-protect" to FEATURES in
* make.conf if you would like the merge to abort in cases like this. You
* can use a command such as `portageq owners / <filename>` 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
* http://bugs.gentoo.org 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):
*
* /opt/bin/atiodcli
* /opt/bin/atiode
* /usr/lib64/opengl/ati/extensions/libglx.so
>>> Merging x11-drivers/ati-drivers-8.552-r2 to /
--- /opt/
--- /opt/sbin/
>>> /opt/sbin/atieventsd
--- /opt/bin/
>>> /opt/bin/atiodcli
>>> /opt/bin/amdcccle
>>> /opt/bin/aticonfig
>>> /opt/bin/atiode
>>> /opt/bin/fglrxinfo
--- /usr/
--- /usr/lib32/
--- /usr/lib32/dri/
>>> /usr/lib32/dri/fglrx_dri.so
--- /usr/lib32/opengl/
--- /usr/lib32/opengl/ati/
!!! Cannot write to '/usr/lib32/opengl/ati/extensions'.
!!! Please check permissions and directories for broken symlinks.
!!! You may start the merge process again by using ebuild:
!!! ebuild /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.552-r2.ebuild merge
!!! And finish by running this: env-update
* Messages for package x11-drivers/ati-drivers-8.552-r2:
* This package will overwrite one or more files that may belong to other
* packages (see list below). Add "collision-protect" to FEATURES in
* make.conf if you would like the merge to abort in cases like this. You
* can use a command such as `portageq owners / <filename>` 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
* http://bugs.gentoo.org 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):
*
* /opt/bin/atiodcli
* /opt/bin/atiode
* /usr/lib64/opengl/ati/extensions/libglx.so
|
My machine is amd64, and I marked "~amd64" on some packages.
My portage.keywords is
Code: |
#For ati-drivers
x11-drivers/ati-drivers ~amd64
x11-base/xorg-server ~amd64
#for xorg-server ~amd64
x11-libs/pixman ~amd64
x11-libs/libpciaccess ~amd64
x11-proto/xproto ~amd64
x11-apps/xauth ~amd64
x11-libs/libXrender ~amd64
x11-proto/renderproto ~amd64
x11-proto/xextproto ~amd64
x11-libs/libXau ~amd64
x11-libs/libXext ~amd64
x11-proto/inputproto ~amd64
x11-libs/xtrans ~amd64
x11-misc/xkeyboard-config ~amd64
media-libs/mesa ~amd64
x11-proto/printproto ~amd64
x11-libs/libdrm ~amd64
x11-libs/libX11 ~amd64
x11-proto/xf86driproto ~amd64
x11-libs/libXxf86vm ~amd64
x11-apps/rgb ~amd64
x11-apps/xinit ~amd64
x11-proto/randrproto ~amd64
x11-libs/libXfont ~amd64
x11-drivers/xf86-video ~amd64
x11-drivers/xf86-video-i128 ~amd64
x11-drivers/xf86-video-fbdev ~amd64
x11-drivers/xf86-input-keyboard ~amd64
x11-drivers/xf86-video-vesa ~amd64
x11-drivers/xf86-video-ati ~amd64
x11-drivers/xf86-video-vmware ~amd64
x11-drivers/xf86-input-mouse ~amd64
x11-drivers/xf86-input-joystick ~amd64
|
I need some helps. |
|
Back to top |
|
|
code_raptor n00b
Joined: 24 Jun 2005 Posts: 47
|
Posted: Wed Dec 03, 2008 12:48 pm Post subject: |
|
|
Looks like that there is a partial merge of the ati-drivers package on the filesystem. Anyway, do a "eselect opengl set xorg-x11", and unmerge the ati-drivers package if is installed. If the files /opt/bin/atiodcli and /opt/bin/atiode are still there u can delete as those are part of the ati-drivers package.
After that check the directories /usr/lib64/opengl/ati/ and /usr/lib32/opengl/ati/, if in there is a broken symlink called "extensions" and delete it. I am sure that broken symlink is the error of "!!! Cannot write to '/usr/lib32/opengl/ati/extensions'."
After that, emerge the ati-drivers package and do a "eselect opengl set ati" _________________ just feel the code... |
|
Back to top |
|
|
haneulso Apprentice
Joined: 31 Aug 2004 Posts: 173
|
Posted: Wed Dec 03, 2008 4:40 pm Post subject: Thanks |
|
|
I'll try it.
Thanks. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|