Richard Fish wrote:
echo dev-libs/dietlibc ~amd64 /etc/portage/package.keywords
I did...
emerge --resume
It still wanted to emerge dietlibc-0.28
If for some reason this tries to merge dietlibc-0.28 again, then do
emerge --oneshot dietlibc
This worked, dietlibc-0.30 has been emerged
On Thursday 07 September 2006 17:30, Jarry wrote:
OMG, again portage wants to re-emerge dietlibc-0.28! Why?
Can I somehow start emerge --resume but without the first
package which previously caused error
(in this case dietlibc-0.28)? I do not want to go over
the whole thing again again, it
On 9/6/06, Jarry [EMAIL PROTECTED] wrote:
Well, gcc upgrade is not so painless as one might think.
Any ideas how to fix this?
Looks like you need to use dietlibc-0.30 with gcc-4.1:
http://bugs.gentoo.org/show_bug.cgi?id=140905
-Richard
--
gentoo-user@gentoo.org mailing list
Richard Fish wrote:
On 9/6/06, Jarry [EMAIL PROTECTED] wrote:
Well, gcc upgrade is not so painless as one might think.
Any ideas how to fix this?
Looks like you need to use dietlibc-0.30 with gcc-4.1:
http://bugs.gentoo.org/show_bug.cgi?id=140905
Hm, but 0.28 is stable, 0.30 is ~ (amd64)
On 9/6/06, Jarry [EMAIL PROTECTED] wrote:
Hm, but 0.28 is stable, 0.30 is ~ (amd64)
Yeah, unfortunately not all of the gcc-4.1 fixes made it to stable
_before_ gcc-4.1. It's too late for the 4.1 upgrade, but as a
userrep, I do plan to raise this as an issue when the next gcc upgrade
cycle
5 matches
Mail list logo
