linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Walnut configuration (old problem)
@ 2002-12-20 12:33 llandre
  2002-12-20 14:59 ` Allen Curtis
  2002-12-20 15:09 ` Wolfgang Denk
  0 siblings, 2 replies; 4+ messages in thread
From: llandre @ 2002-12-20 12:33 UTC (permalink / raw)
  To: linuxppc-embedded


I've just start working with the Walnut board. I downloaded:
1) linuxppc_2_4 with rsync
2) linuxppc_2_4_devel with rsync
3) linuxppc_2_4_devel with bk

but in all cases I encountered the same problem described here
http://lists.linuxppc.org/linuxppc-embedded/200207/msg00005.html.

I followed the instructions proposed here
http://lists.linuxppc.org/linuxppc-embedded/200207/msg00006.html but this
didn't solve the problem.

Anybody can help me?

Thanks in advance,

llandre

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Walnut configuration (old problem)
  2002-12-20 12:33 Walnut configuration (old problem) llandre
@ 2002-12-20 14:59 ` Allen Curtis
  2002-12-20 15:09 ` Wolfgang Denk
  1 sibling, 0 replies; 4+ messages in thread
From: Allen Curtis @ 2002-12-20 14:59 UTC (permalink / raw)
  To: llandre, linuxppc-embedded


> I've just start working with the Walnut board. I downloaded:
> 1) linuxppc_2_4 with rsync
> 2) linuxppc_2_4_devel with rsync
> 3) linuxppc_2_4_devel with bk
>

make ARCH=ppc walnut_config


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Walnut configuration (old problem)
  2002-12-20 12:33 Walnut configuration (old problem) llandre
  2002-12-20 14:59 ` Allen Curtis
@ 2002-12-20 15:09 ` Wolfgang Denk
  1 sibling, 0 replies; 4+ messages in thread
From: Wolfgang Denk @ 2002-12-20 15:09 UTC (permalink / raw)
  To: llandre; +Cc: linuxppc-embedded


In message <5.1.1.6.0.20021220132028.02337438@dns.struinfo.it> you wrote:
>
> I've just start working with the Walnut board. I downloaded:
> 1) linuxppc_2_4 with rsync
> 2) linuxppc_2_4_devel with rsync
> 3) linuxppc_2_4_devel with bk
>
> but in all cases I encountered the same problem described here
> http://lists.linuxppc.org/linuxppc-embedded/200207/msg00005.html.

Did you remember to set (in the top level Makefile) the definition of
ARCH to "ppc"?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
You are only young once, but you can stay immature indefinitely.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Walnut configuration (old problem)
@ 2002-12-23 13:49 llandre
  0 siblings, 0 replies; 4+ messages in thread
From: llandre @ 2002-12-23 13:49 UTC (permalink / raw)
  To: linuxppc-embedded


Sorry for my silly question.
I didn't realize that even in the Linux PPC master Makefile it is necessary
to setup the ARCH variable.
Anyway here are the operations I performed in order to build the kernel for
this board (I think this can help other newbies like me):

1) download linuxppc_2_4_devel tree: rsync -avz --delete
source/mvista.com::linuxppc_2_4_devel <destination_directory>
2) make mrproper
3) make walnut_config
4) make oldconfig
5) make dep
6) make pImage


Thanks for the help,

llandre


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-12-23 13:49 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-20 12:33 Walnut configuration (old problem) llandre
2002-12-20 14:59 ` Allen Curtis
2002-12-20 15:09 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2002-12-23 13:49 llandre

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).