From: Matt Porter <porter@cox.net>
To: Nico Schottelius <schottelius@wdt.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ppc cross compiling...
Date: Fri, 28 Feb 2003 05:56:11 -0700 [thread overview]
Message-ID: <20030228055611.A18247@home.com> (raw)
In-Reply-To: <20030228112429.GD328@schottelius.org>; from schottelius@wdt.de on Fri, Feb 28, 2003 at 12:24:29PM +0100
On Fri, Feb 28, 2003 at 12:24:29PM +0100, Nico Schottelius wrote:
> Hello!
>
> I am trying to cross compile 2.5.64 and get the following
> compile errors:
>
> make -f scripts/Makefile.build obj=arch/ppc/mm
> powerpc-linux-gcc -Wp,-MD,arch/ppc/mm/.4xx_mmu.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -I/usr/src/linux-2.5.50/arch/ppc -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -Wa,-m405 -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=4xx_mmu -DKBUILD_MODNAME=4xx_mmu -c -o arch/ppc/mm/4xx_mmu.o arch/ppc/mm/4xx_mmu.c
> arch/ppc/mm/4xx_mmu.c: In function `mmu_mapin_ram':
> arch/ppc/mm/4xx_mmu.c:99: `phys_addr_t' undeclared (first use in this function)
Whoa, wait a minute. Don't expect to have PPC (especially 4xx stuff) to
even build (much less run) in Linus' tree. A number of things that are
under heavy development have not been submitted. You need to grab
the PPC development tree, see http://penguinppc.org/dev/kernel.shtml
for instructions on pulling the linuxppc-2.5 tree. In this case
the phys_addr_t declaration in mmu.h hasn't found its way up.
Also, these questions are more appropriate for the linuxppc-dev or
linuxppc-embedded lists (http://lists.linuxppc.org/) where all the
PPC developers can be found.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
prev parent reply other threads:[~2003-02-28 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 11:24 Nico Schottelius
2003-02-28 12:56 ` Matt Porter [this message]
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=20030228055611.A18247@home.com \
--to=porter@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schottelius@wdt.de \
/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
all inboxes | Powered by JetHome®