From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-mips@linux-mips.org
Subject: Re: Exception while loading kernel
Date: Fri, 31 Aug 2007 07:49:03 +0200 [thread overview]
Message-ID: <1188539343.18249.2.camel@scarafaggio> (raw)
In-Reply-To: <816d36d30708290305i4b34ae11s4b469cc48fb999aa@mail.gmail.com>
Il giorno mer, 29/08/2007 alle 06.05 -0400, Ricardo Mendoza ha scritto:
> On 8/29/07, Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org> wrote:
>
> > I already tried the 32bit kernel and I found the same problem. Are you
> > telling me that I should use 32bit for debugging instead of 64?
>
> No, what I'm telling you to do is to try and build it with
> CONFIG_BUILD_ELF64 disabled, more explicitly that is under Executable
> file formats or something like that. About kgdb debugging, what I am
> telling you is that ip32 has no hook ups coded for it yet, in other
> words, no support.
I tried recompiling the 2.6.23-rc3 from linux-mips.org with
CONFIG_BUILD_ELF64=n, but I got a compiler error:
CC [M] net/sched/em_nbyte.o
CC [M] net/sched/em_u32.o
CC [M] net/sched/em_meta.o
net/sched/em_meta.c: In function ‘meta_int_loadavg_0’:
net/sched/em_meta.c:127: error: PRINT_OPERAND, invalid operand for relocation
(const:DI (plus:DI (symbol_ref:DI ("avenrun") [flags 0x40] <var_decl 0x2b357f50 avenrun>)
(const_int 4 [0x4])))
net/sched/em_meta.c:127: internal compiler error: in print_operand_reloc, at config/mips/mips.c:5579
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
{standard input}: Assembler messages:
{standard input}:2436: Warning: end of file not at end of a line; newline inserted
{standard input}:2547: Warning: missing .end at end of assembly
Preprocessed source stored into /tmp/cc0KjlCH.out file, please attach this to your bugreport.
make[3]: *** [net/sched/em_meta.o] Error 1
make[2]: *** [net/sched] Error 2
make[1]: *** [net] Error 2
make[1]: Leaving directory `/usr/local/src/linux-2.6.23-rc3'
make: *** [debian/stamp-build-kernel] Error 2
I will try to submit the bug report to gcc.
Bye,
Giuseppe
next prev parent reply other threads:[~2007-08-31 5:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1188030215.13999.14.camel@scarafaggio>
2007-08-27 6:36 ` Exception while loading kernel Giuseppe Sacco
2007-08-27 6:36 ` Giuseppe Sacco
2007-08-27 13:01 ` Markus Gothe
2007-08-27 13:17 ` Giuseppe Sacco
2007-08-28 17:18 ` Giuseppe Sacco
2007-08-29 2:25 ` Markus Gothe
2007-08-29 6:46 ` Giuseppe Sacco
2007-08-29 8:33 ` Ricardo Mendoza
2007-08-29 8:54 ` Giuseppe Sacco
2007-08-29 10:05 ` Ricardo Mendoza
2007-08-29 16:51 ` Markus Gothe
2007-08-29 21:30 ` Ricardo Mendoza
2007-08-31 5:49 ` Giuseppe Sacco [this message]
2007-08-31 7:14 ` Markus Gothe
2007-08-31 7:41 ` Giuseppe Sacco
2007-08-30 12:52 ` Giuseppe Sacco
2007-08-30 12:52 ` Giuseppe Sacco
2007-08-30 20:04 ` Markus Gothe
2007-08-30 21:20 ` Giuseppe Sacco
[not found] ` <20070825152536.GA4499@networkno.de>
[not found] ` <Pine.SGI.4.60.0708252047260.4891@zeus.tetracon-eng.net>
[not found] ` <20070826065054.84c97aef.giuseppe@eppesuigoccas.homedns.org>
[not found] ` <Pine.LNX.4.64.0708300931100.14430@pixie.tetracon-eng.net>
[not found] ` <1188481891.6770.22.camel@scarafaggio>
2007-09-06 10:58 ` J. Scott Kasten
2007-09-06 11:57 ` Giuseppe Sacco
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=1188539343.18249.2.camel@scarafaggio \
--to=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.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