Michael wrote:
>> Nice to know I'm not alone.  I forgot to mention, it wanted to update
>> glibc first.  The news item said NOT to let it do that and use the
>> --nodeps option instead.  So, the command I used had that option.  I've
>> since restarted it, just in case it finishes.  I'll post back if it
>> does.  I find it odd that it builds fine one time but fails on others. 
>> Strange things happen tho. 
>>
>> Dale
>>
>> :-)  :-) 
> There's a new patch for gcc.  You need to follow the guide as you did, then 
> resync portage to fetch the latest ebuild for gcc, before you start the emerge 
> --emptytree world.  This is how I managed to get ggc to build after previous 
> attempts with 'no error' failures.  Hope this works for you.


It just failed the second attempt.  I'll sync again and hopefully the
new ebuild will fix things.  If nothing else, they working out the
kinks.  Since I'm in a chroot, messing up won't matter. 

Maybe Peter will see this, update and try again.  May help him as well. 

Thanks.

Dale

:-)  :-)