From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: Jonathan Day <imipak@yahoo.com>, linux-mips@linux-mips.org
Subject: Re: Another problem with compiling Linux kernel
Date: Wed, 16 Nov 2005 15:19:56 +0000 [thread overview]
Message-ID: <20051116151956.GG3229@linux-mips.org> (raw)
In-Reply-To: <437A5511.8020806@avtrex.com>
On Tue, Nov 15, 2005 at 01:37:21PM -0800, David Daney wrote:
> >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.
> >
>
> This is not a GCC bug, but a change in GCC behavior. One patch was
> posted here:
>
> http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=Pine.LNX.4.61.0511022057140.3511%40trantor.stuart.netsweng.com
>
> I don't know if the change made it into the linux-mips git repository or
> not.
That patch has a few shortcomings, so I didn't apply it yet. Unfortunately
a proper solution turns out to be a pretty hard nut.
Ralf
next prev parent reply other threads:[~2005-11-16 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 21:30 Another problem with compiling Linux kernel Jonathan Day
2005-11-15 21:37 ` David Daney
2005-11-16 15:19 ` Ralf Baechle [this message]
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=20051116151956.GG3229@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@avtrex.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.