From: "Kyle Unice" <unixe@comcast.net>
To: "'Brett Foster'" <fosterb@uoguelph.ca>
Cc: <linux-mips@linux-mips.org>
Subject: RE: Cross-compiling Linux problem
Date: Fri, 7 Oct 2005 15:26:49 -0600 [thread overview]
Message-ID: <002c01c5cb85$d42c5050$0400a8c0@buzz> (raw)
In-Reply-To: <4346DD97.40106@uoguelph.ca>
I am compiling the db1550_defconfig which does define
CONFIG_64BIT_PHYS_ADDR.
The cross compiler is mipsel generated from crosstool.sh
Kyle
-----Original Message-----
From: Brett Foster [mailto:fosterb@uoguelph.ca]
Sent: Friday, October 07, 2005 2:42 PM
To: Kyle Unice
Cc: linux-mips@linux-mips.org
Subject: Re: Cross-compiling Linux problem
Kyle Unice wrote:
>arch/mips/mm/tlbex.c:516:5: warning: "CONFIG_64BIT" is not defined
> AS arch/mips/mm/tlbex-fault.o
> CC arch/mips/mm/ioremap.o
>arch/mips/mm/ioremap.c: In function `__ioremap':
>include/asm-mips/mach-au1x00/ioremap.h:15: sorry, unimplemented: inlining
>failed
> in call to '__fixup_bigphys_addr': function body not available
>arch/mips/mm/ioremap.c:28: sorry, unimplemented: called from here
>make[1]: *** [arch/mips/mm/ioremap.o] Error 1
>make: *** [arch/mips/mm] Error 2
>
>
I once had this sort of problem when I forgot to specify the cross
compiler while invoking make and tried to compile a MIPS kernel on X86 gcc.
Brett
WARNING: multiple messages have this Message-ID (diff)
From: "Kyle Unice" <unixe@comcast.net>
To: 'Brett Foster' <fosterb@uoguelph.ca>
Cc: linux-mips@linux-mips.org
Subject: RE: Cross-compiling Linux problem
Date: Fri, 7 Oct 2005 15:26:49 -0600 [thread overview]
Message-ID: <002c01c5cb85$d42c5050$0400a8c0@buzz> (raw)
Message-ID: <20051007212649.d5O747lMYhGEN2MFOj9LWBE_hZxmR6isaM3MncS7tNI@z> (raw)
In-Reply-To: <4346DD97.40106@uoguelph.ca>
I am compiling the db1550_defconfig which does define
CONFIG_64BIT_PHYS_ADDR.
The cross compiler is mipsel generated from crosstool.sh
Kyle
-----Original Message-----
From: Brett Foster [mailto:fosterb@uoguelph.ca]
Sent: Friday, October 07, 2005 2:42 PM
To: Kyle Unice
Cc: linux-mips@linux-mips.org
Subject: Re: Cross-compiling Linux problem
Kyle Unice wrote:
>arch/mips/mm/tlbex.c:516:5: warning: "CONFIG_64BIT" is not defined
> AS arch/mips/mm/tlbex-fault.o
> CC arch/mips/mm/ioremap.o
>arch/mips/mm/ioremap.c: In function `__ioremap':
>include/asm-mips/mach-au1x00/ioremap.h:15: sorry, unimplemented: inlining
>failed
> in call to '__fixup_bigphys_addr': function body not available
>arch/mips/mm/ioremap.c:28: sorry, unimplemented: called from here
>make[1]: *** [arch/mips/mm/ioremap.o] Error 1
>make: *** [arch/mips/mm] Error 2
>
>
I once had this sort of problem when I forgot to specify the cross
compiler while invoking make and tried to compile a MIPS kernel on X86 gcc.
Brett
next prev parent reply other threads:[~2005-10-07 21:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 20:18 Cross-compiling Linux problem Kyle Unice
2005-10-07 20:18 ` Kyle Unice
2005-10-07 20:41 ` Brett Foster
2005-10-07 20:54 ` Maciej W. Rozycki
2005-10-07 21:26 ` Kyle Unice [this message]
2005-10-07 21:26 ` Kyle Unice
2005-10-07 21:47 ` Pete Popov
2005-10-07 21:54 ` Kyle Unice
2005-10-07 21:54 ` Kyle Unice
2005-10-07 22:27 ` David Daney
2005-10-07 22:56 ` Ilya A. Volynets-Evenbakh
2005-10-07 23:15 ` David Daney
2005-10-08 13:52 ` Kyle Unice
2005-10-08 13:52 ` Kyle Unice
2005-10-13 11:58 ` Ralf Baechle
2005-10-13 12:07 ` Ralf Baechle
2005-10-08 3:33 ` Kyle Unice
2005-10-08 3:33 ` Kyle Unice
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='002c01c5cb85$d42c5050$0400a8c0@buzz' \
--to=unixe@comcast.net \
--cc=fosterb@uoguelph.ca \
--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.