Summary: | revdep-rebuild => not able to pass emerge gcc .... | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Roman Gruber <roman.gruber> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | trivial | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roman Gruber
2009-09-18 09:35:32 UTC
(In reply to comment #0) > emerge: there are no ebuilds to satisfy > "sys-devel/gcc:x86_64-pc-linux-gnu-4.3.4". This looks loke a cross-compile slot but I am not sure. Out of curiosity: What did you do to break gcc? I am not sure that you will able to recompile gcc if your current version is already broken... I know having multiple gcc*s is safer then one. So I have 3 or 4 versions installed. Last time I had one gcc and I did a hole reinstallation of the box. This system gave me the bug and the box is a reinstallation, which is only one week old!! So there are no old dependencies or broken packages or something like that. I only did change some useflags to get closer to my old setup. Well I use sane gcc flags, no insane. Dont ask me why. System is on lvm + luks + ext4 There really is no perfect way to implement something like revdep-rebuild for packages that have USE=multislot enabled. See bug #287900, comment #5 for and explanation of why this is the case. *** This bug has been marked as a duplicate of bug 254397 *** (In reply to comment #4) > > *** This bug has been marked as a duplicate of bug 254397 *** > Ok thx, I do write some bugs report over the year, but I am an advanced user who has no knowledge about portage internals. Well I like gentoo, and I also have arch linux, but its much worse then gentoo. Great work, if there is no solution jet, i accept it! |