From: "Mathias W." <m.weigt@uni-bonn.de>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Problems with mips-sources-2.6.20
Date: Sun, 10 Jun 2007 17:23:21 +0200 [thread overview]
Message-ID: <466C1769.1060807@uni-bonn.de> (raw)
In-Reply-To: <20070610104104.7096c7b1@azathoth.beerandrocks.net>
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@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-10 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 14:35 [gentoo-mips] Problems with mips-sources-2.6.20 Mathias W.
2007-06-10 14:41 ` Stephen P. Becker
2007-06-10 15:23 ` Mathias W. [this message]
2007-06-10 17:16 ` Kumba
2007-06-10 19:46 ` Mathias W.
2007-06-11 13:18 ` Mathias W.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466C1769.1060807@uni-bonn.de \
--to=m.weigt@uni-bonn.de \
--cc=gentoo-mips@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox