From: Jonathan Day <imipak@yahoo.com>
To: linux-mips@linux-mips.org
Subject: Another problem with compiling Linux kernel
Date: Tue, 15 Nov 2005 13:30:05 -0800 (PST) [thread overview]
Message-ID: <20051115213005.79456.qmail@web31513.mail.mud.yahoo.com> (raw)
Hi again,
Using GCC 4.0.0 on the Broadcom SB1 MIPS64 board, the
compilation crashes at the final link phase with the
following errors:
`.exit.text' referenced in section `.pdr.78' of
arch/mips/kernel/built-in.o: defined in discarded
section `.exit.text' of arch/mips/kernel/built-in.o
`.exit.text' referenced in section `.pdr.37' of
fs/built-in.o: defined in discarded section
`.exit.text' of fs/built-in.o
`.exit.text' referenced in section `.pdr.17' of
crypto/built-in.o: defined in discarded section
`.exit.text' of crypto/built-in.o
`.exit.text' referenced in section `.pdr.17' of
block/built-in.o: defined in discarded section
`.exit.text' of block/built-in.o
`.exit.text' referenced in section `.pdr.10' of
drivers/built-in.o: defined in discarded section
`.exit.text' of drivers/built-in.o
`.exit.data' referenced in section `.exit.text.403' of
net/built-in.o: defined in discarded section
`.exit.data' of net/built-in.o
`.exit.data' referenced in section `.exit.text.403' of
net/built-in.o: defined in discarded section
`.exit.data' of net/built-in.o
`.exit.data' referenced in section `.exit.text.403' of
net/built-in.o: defined in discarded section
`.exit.data' of net/built-in.o
`.exit.data' referenced in section `.exit.text.403' of
net/built-in.o: defined in discarded section
`.exit.data' of net/built-in.o
`.exit.text' referenced in section `.pdr.20' of
net/built-in.o: defined in discarded section
`.exit.text' of net/built-in.o
My first thought was "ah, might be because I'm using
an old GCC, so I'll try something more recent and see
what happens". When trying GCC 4.1.0 (snapshot from
20051017), I get the following error:
In file included from include/linux/nfs_fs.h:15,
from init/do_mounts.c:12:
include/linux/pagemap.h: In function
'fault_in_pages_readable':
include/linux/pagemap.h:237: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:237: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:237: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:237: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:243: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:243: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:243: error: read-only variable
'__gu_val' used as 'asm' output
include/linux/pagemap.h:243: error: read-only variable
'__gu_val' used as 'asm' output
make[1]: *** [init/do_mounts.o] Error 1
make: *** [init] Error 2
This one may be a compiler bug (experimental GCCs are,
well, experimental!) but it makes it somewhat harder
to know if the later issue is resolved by using a
different toolchain.
Any suggestions on how to fix either/both problems?
Thanks,
Jonathan Day
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
next reply other threads:[~2005-11-15 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 21:30 Jonathan Day [this message]
2005-11-15 21:37 ` Another problem with compiling Linux kernel David Daney
2005-11-16 15:19 ` Ralf Baechle
2005-11-16 11:15 ` Thiemo Seufer
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=20051115213005.79456.qmail@web31513.mail.mud.yahoo.com \
--to=imipak@yahoo.com \
--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