Hmmmm 'k, guys - sort this out please, it sucks... ktnx. ;) I suspect gcc is not the only slotted thing in portage that will blow... * checking 562 files for package collisions existing file /sbin/fix_libtool_files.sh is not owned by this package existing file /lib/rcscripts/awk/fixlafiles.awk is not owned by this package * spent 0.168200969696 seconds checking for file collisions * 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 # equery b /sbin/fix_libtool_files.sh [ Searching for file(s) /sbin/fix_libtool_files.sh in *... ] sys-devel/gcc-3.4.4-r1 (/sbin/fix_libtool_files.sh) sys-devel/gcc-4.0.3 (/sbin/fix_libtool_files.sh) # equery b /lib/rcscripts/awk/fixlafiles.awk [ Searching for file(s) /lib/rcscripts/awk/fixlafiles.awk in *... ] sys-devel/gcc-3.4.4-r1 (/lib/rcscripts/awk/fixlafiles.awk) sys-devel/gcc-4.0.3 (/lib/rcscripts/awk/fixlafiles.awk)
*** This bug has been marked as a duplicate of 87647 ***
Reopening, the fix for Bug 87647 doesn't solve this issue.
*** This bug has been marked as a duplicate of 90744 ***
Sigh. Have you got bunch of more candidates for duping this bug against? It fails now and needs to be fixed, whether the tool itself sucks or not. Anyone upgrading gcc to another slot will hit this w/ recent portage, waiting for a bug that isn't even close to a solution after one year is not a viable option.
as i told you on irc, we're handling this in another way, so having a bug report open does nothing so leave it be *** This bug has been marked as a duplicate of 90744 ***
*** Bug 134390 has been marked as a duplicate of this bug. ***
*** Bug 135374 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > as i told you on irc, we're handling this in another way, so having a bug > report open does nothing Well, the problem still exists over a month later, even though bug #90744 is marked FIXED. Having a bug open allows people to see that it hasn't yet been fixed, and allows it to appear on default bug searches (thus reducing dups). Closing it before the problem is actually fixed doesn't help anyone, as far as I can tell. More significantly there's more to the collisions that just the libtool files stuff: Collision list from gcc-4.0.3: /sbin/fix_libtool_files.sh /lib/rcscripts/awk/fixlafiles.awk /usr/lib/pkgconfig/libgcj.pc The first two could be dealt with simply by: 1) installing in postinst (i.e. taking them out of the package database) 2) making them a separate build (gcc-utils perhaps) and DEPENDing on it since they're bits added by Gentoo. The last is potentially more serious. Could perhaps move the pkgconfig directory to: /usr/lib/${CTARGET}/pkgconfig in ${D} before merge and have gcc-config/eselect-compiler soft-link from the selected target to /usr/lib/pkgconfig - I haven't a clue what it's used for, but it's part of libjava.
(In reply to comment #8) > Could perhaps move the pkgconfig directory to: > > /usr/lib/${CTARGET}/pkgconfig maybe not, after finding out what it's for :) Still, /usr/lib/pkgconfig/libgcj.pc needs to be slotted somehow. Perhaps moving it to /usr/lib/pkgconfig/libgcj-<gcc version>.pc and softlinking to /usr/lib/pkgconfig/libgcj.pc
different issue with .pc files file a new bug
bug #136382 filed for libgcj.pc. In the meantime, could you explain how you don't get collisions on /sbin/fix_libtool_files.sh and /lib/rcscripts/awk/fixlafiles.awk, since you've marked this bug WORKSFORME?
