On Sunday 17 August 2003 18:12, Tony Clark wrote: > On Sunday 17 August 2003 10.19, Jason Stubbs wrote: > > On Sunday 17 August 2003 17:08, Tony Clark wrote: > > > On Sunday 17 August 2003 08.54, Jason Stubbs wrote: > > > > Hello all, > > > > > > > > I know this was covered previously, but a proper solution was not > > > > given. I've done everything I can think of to unmask gcc331, but > > > > "emerge -uDp world" still wants to downgrade it. Even "emerge -UDp > > > > world" wants to downgrade it! > > > > > > > > I haven't bothered with packages.mask causing grepping it for gcc > > > > doesn't give anything for the version I want to use. In the ebuild > > > > itself I find "KEYWORDS='-*'" which I've changed to "KEYWORDS='~x86'" > > > > but it hasn't made a difference. > > > > /usr/portage/metadata/cache/sys-devel/gcc-3.3.1 also contained "-*" > > > > which I changed to "~x86" and it still makes no difference. I've even > > > > tried PORTAGE_OVERLAY but no cigar. > > > > > > > > I've checked all the dependencies and have all the required packages > > > > installed; i.e. it's not a package further down the tree that's > > > > masked. I honestly cannot see what I'm missing. The gcc33 forum says > > > > to unmask it in packages.mask but it's not in there - at least not > > > > anymore. Any suggestions? > > > > > > Just copy it to your PORTAGE_OVERLAY directory and make it stable. > > > "x86" > > > > As I said, I tried the PORTAGE_OVERLAY but it didn't work. True, I used > > "KEYWORDS='~x86'" but I've got "ACCEPT_KEYWORDS='~x86'" in make.conf. But > > just to be thorough, I changed it to 'x86' and it still doesn't work. > > ok I did a little test, what I said before worked ok with glibc but not > with gcc. I copied the gcc-3.3.1.ebuild to gcc-3.3.1-r1.ebuild and "x86" > in portage local and that fixed the problem for me. > k, found and fixed the problem. I tried changing default-x86-1.4/packages like Volker said and got a depgraph creation failure due to glibc depending on gcc-3.2. Checking glibc-2.3.2-r1.ebuild, sure enough I found "=gcc-3.2*". Unmasking glibc-2.3.2-r3 fixed everything.
Thanks for all your help! Jason -- [EMAIL PROTECTED] mailing list
