From: David Daney <ddaney@avtrex.com>
To: sjhill@realitydiluted.com
Cc: crossgcc@sources.redhat.com, MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: linux kernel building for mips malta target board
Date: Wed, 02 Nov 2005 16:45:40 -0800 [thread overview]
Message-ID: <43695DB4.7060708@avtrex.com> (raw)
In-Reply-To: <E1EXLJV-0005R4-K3@real.realitydiluted.com>
sjhill@realitydiluted.com wrote:
>>>I would like to build latest kernel (ie kernel 2.6.13) for mips malta
>>>board. Can any one advise me the cross-compiler tools version to be
>>>used for building the linux kernel.
>>>
>>
>>I use both gcc-3.3.1 and gcc-3.4.3 to build 2.6.x mips linux kernels. I
>>think for the 2.6.13 kernel any of the latest released versions of
>>3.3.x, 3.4.x, or 4.0.x would work. Use the latest binutils (2.16.91
>>20050817 is what I am using).
>>
>
> Also, make sure to NOT use any of the 4.1 GCC stuff with Linux/MIPS
> kernels. I am still tracking down errors with it.
>
Is this the problem you are seeing?:
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:236: error: read-only variable ‘__gu_val’ used
as ‘asm’ output
include/linux/pagemap.h:236: error: read-only variable ‘__gu_val’ used
as ‘asm’ output
include/linux/pagemap.h:236: error: read-only variable ‘__gu_val’ used
as ‘asm’ output
include/linux/pagemap.h:236: error: read-only variable ‘__gu_val’ used
as ‘asm’ output
The compiler behavior has changed since 4.0.1, but I think the new
behavior is correct. I am blaming the __get_user macro in
include/asm-mips/uaccess.h. It should be possible to fix it there. The
alternative is to hack up include/linux/pagemap.h.
David Daney
next parent reply other threads:[~2005-11-03 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EXLJV-0005R4-K3@real.realitydiluted.com>
2005-11-03 0:45 ` David Daney [this message]
2005-11-03 1:02 ` linux kernel building for mips malta target board Stuart Anderson
2005-11-03 1:19 ` David Daney
2005-11-03 2:20 ` Stuart Anderson
2005-11-03 16:33 ` Ralf Baechle
2006-01-18 12:52 ` Martin Michlmayr
2006-01-18 13:05 ` Ralf Baechle
2006-01-18 13:37 ` Martin Michlmayr
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=43695DB4.7060708@avtrex.com \
--to=ddaney@avtrex.com \
--cc=crossgcc@sources.redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@realitydiluted.com \
/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