Stephen P. Becker schrieb:
>> oldconfig) and it doesn't boot. I get the same message as in this
>> thread: http://archives.gentoo.org/gentoo-mips/msg_00503.xml
>>
>> NESTED EXCEPTION #1 (vid 0) at EPC: ffffffff9fc6a0a4; first exception
>> at PC: 0
>>
>> Several weeks before I tried 2.6.20.6 (which wasn't marked stable)
>> and couldn't get this to boot either. The system is uptodate. Here is
>> my toolchain: gcc-config -l
>>  [1] mips64-unknown-linux-gnu-3.4.6 *
>>  [2] mips64-unknown-linux-gnu-4.1.1
>>  [3] mips-unknown-linux-gnu-3.4.6 *
>>  [4] mips-unknown-linux-gnu-3.4.6-hardenednopiessp
>>  [5] mips-unknown-linux-gnu-4.1.1
>>
>> Any new suggestions to solve this apparently known problem?
>>
> 
> Have you tried to build your kernel with gcc-4.1.1 instead of 3.4.6?

Not yet, because this is the only system, where the kernel builds. On the other system(s) I still have problems like
this:  http://archives.gentoo.org/gentoo-mips/msg_00571.xml
I know that the bug http://bugs.gentoo.org/show_bug.cgi?id=171486 is fixed with the new binutils-config but I still
don't get a vmlinux on this system because of the same error as in comment 7 of this bug
(http://bugs.gentoo.org/show_bug.cgi?id=171486#c7). And this all happened after switching to gcc-4.1...

But I'll try to do it now and see if it will break.

-- 
Mathias Weigt


-- 
gentoo-mips@g.o mailing list