From: "John Rigby" <jcrigby@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel for MPC Lite 5200 will not compile
Date: Mon, 27 Mar 2006 18:01:28 -0700 [thread overview]
Message-ID: <4b73d43f0603271701q24910d9rf4e61e5136c2b727@mail.gmail.com> (raw)
In-Reply-To: <20060328000703.GA95672@server.idefix.loc>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
try make lite5200_defconfig instead of copying it to .config
or make oldconfig after copying ti to .config
On 3/27/06, Matthias Fechner <idefix@fechner.net> wrote:
>
> Hi,
>
> I installed today ELDK 4.0 for the LITE5200 board (icecube).
> ./install -d /usr/local/eldk ppc_6xx
>
> After compiling u-boot and playing a little bit with it, i tried to
> compile the kernel 2.6.
>
> For this I used the git repository.
> I copied the file arch/ppc/configs/lite5200_defconfig to .config, and
> tried the following one:
> make ARCH=ppc CROSS_COMPILE=ppc_6xx- uImage
>
> But i got a failure with the following error message:
> CC arch/ppc/syslib/bestcomm/bestcomm.o
> arch/ppc/syslib/bestcomm/bestcomm.c: In function 'mpc52xx_sdma_probe':
> arch/ppc/syslib/bestcomm/bestcomm.c:269: warning: implicit declaration of
> function 'to_platform_device'
> arch/ppc/syslib/bestcomm/bestcomm.c:269: warning: initialization makes
> pointer from integer without a cast
> arch/ppc/syslib/bestcomm/bestcomm.c:278: warning: implicit declaration of
> function 'platform_get_resource'
> arch/ppc/syslib/bestcomm/bestcomm.c:278: warning: assignment makes pointer
> from integer without a cast
> arch/ppc/syslib/bestcomm/bestcomm.c:279: warning: assignment makes pointer
> from integer without a cast
> arch/ppc/syslib/bestcomm/bestcomm.c: At top level:
> arch/ppc/syslib/bestcomm/bestcomm.c:367: error: 'platform_bus_type'
> undeclared here (not in a function)
> make[2]: *** [arch/ppc/syslib/bestcomm/bestcomm.o] Fehler 1
> make[1]: *** [arch/ppc/syslib/bestcomm] Fehler 2
> make: *** [arch/ppc/syslib] Fehler 2
>
> What is wrong here, I think i did an error on any step...
>
> Thx for help!
>
> Best regards,
> Matthias
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: Type: text/html, Size: 2356 bytes --]
next prev parent reply other threads:[~2006-03-28 1:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:07 Kernel for MPC Lite 5200 will not compile Matthias Fechner
2006-03-28 1:01 ` John Rigby [this message]
2006-03-28 9:49 ` Matthias Fechner
2006-03-28 16:15 ` John Rigby
2006-03-28 20:47 ` Sylvain Munaut
2006-03-29 15:32 ` Matthias Fechner
2006-04-01 9:19 ` Matthias Fechner
2006-04-02 17:42 ` Sylvain Munaut
2006-04-02 19:32 ` Matthias Fechner
2006-03-28 22:33 ` Wolfgang Denk
2006-03-29 15:31 ` Matthias Fechner
2006-03-28 22:31 ` Wolfgang Denk
2006-03-29 15:39 ` Matthias Fechner
2006-03-29 20:11 ` Wolfgang Denk
2006-03-29 23:02 ` Sylvain Munaut
2006-03-30 0:34 ` Wolfgang Denk
2006-03-30 6:36 ` Sylvain Munaut
2006-03-30 16:29 ` John Rigby
2006-03-30 16:39 ` John Rigby
2006-03-30 20:05 ` Dale Farnsworth
2006-03-30 21:51 ` John Rigby
2006-03-30 19:53 ` Dale Farnsworth
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=4b73d43f0603271701q24910d9rf4e61e5136c2b727@mail.gmail.com \
--to=jcrigby@gmail.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).