Collisions when compiling glibc-2.5-r3 and r4 on amd64

Thread: Collisions when compiling glibc-2.5-r3 and r4 on amd64

Search this list only Search all lists
Collisions when compiling glibc-2.5-r3 and r4 on amd64
Germany	2007-07-14 19:55:10
[As posted to gentoo-user, along with small corrections and updates!] Hi List, I didn't find any bug report matching my experience. This appears to be the closest match: http://bugs.gentoo.org/show_bug.cgi?id=145749. I thought I'd ask about it here first, before reporting a bug, in the event of PEBKAC. I updated linux-headers today to the current stable, 2.6.21, and the messages recommend a recompile of the system libc, in this case glibc. When it wants to merge the compiled glibc, I get this: [------------------------------------------------------------] >>> Completed installing glibc-2.5-r4 into /var/tmp/portage/sys-libs/glibc-2.5-r4/image/ ecompressdir: bzip2 -9 usr/share/man ecompressdir: bzip2 -9 /usr/share/info making executable: usr/lib32/libc.so making executable: usr/lib32/libpthread.so making executable: usr/lib64/libc.so making executable: usr/lib64/libpthread.so * checking 2373 files for package collisions 1000 files checked ... 2000 files checked ... existing file /lib is not owned by this package * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package sys-libs/glibc-2.5-r4 NOT merged Searching all installed packages for file collisions... Press Ctrl-C to Stop * x11-drivers/nvidia-drivers-1.0.9746-r1: '/lib' * sys-boot/grub-0.97-r3: '/lib' * media-sound/alsa-firmware-1.0.14_rc2-r1: '/lib' * media-sound/alsa-driver-1.0.14_rc2-r1: '/lib' * sys-fs/udev-104-r12: '/lib' * sys-fs/cryptsetup-luks-1.0.4-r3: '/lib' * sys-fs/device-mapper-1.02.19: '/lib' * sys-fs/lvm2-2.02.10: '/lib' * media-libs/libgphoto2-2.2.1-r1: '/lib' * sys-apps/hal-0.5.9-r1: '/lib' * net-analyzer/macchanger-1.5.0-r1: '/lib' marcec marcec # [------------------------------------------------------------] Is there a 'clean' work around? The only option I found is to set COLLISION_IGNORE="/lib" in make.conf. That seems to do the trick insofar that glibc merges. For "emerge --info" see attachment. Apparently, from what I read, the collision-protect[1] option is supposed to ignore directories. Since this was asked in other reports I found while searching for info: /lib is not a symlink, rather /lib64 is a symlink to /lib. Out of curiosity: when would /lib ever be a symlink? Note that I will not have my email available for a few days starting tonight (Sunday). I'm sending my PC via mail to my home for the summer holidays, versus it staying in my dorm room. Yes I know of VNC, but I didn't find the time to set it up. Any help greatly appreciated! -- Marc Joliet [1] I only semi-recently (a few weeks ago) set the collision-protect option, and until now, glibc is the only package to complain. -- Marc Joliet
Approximate file size 5816 bytes