All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
To: sébastien tadéoni <sebastien_tadeoni@yahoo.fr>
Cc: linux ppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Questions on the MPC8xx-2.3.10 realease.
Date: Fri, 24 Sep 1999 10:37:53 +1000	[thread overview]
Message-ID: <37EAC7E0.3AE82656@ctam.com.au> (raw)
In-Reply-To: 19990923150552.23602.rocketmail@web601.yahoomail.com


sébastien tadéoni wrote:

> Hi PPCpeople;
>
> I worked recently on the mpc8xx-2.3.10 sources, and I
> had less problem for compilation than with the 2.2.5
> release, but it stays some 'undefined reference to
> :kbd_pt_regs, fg_console, no_scroll.....'.
>
> I think it is a configuration problem, but I don't
> find any solution (and I wonder if I will find the
> good configuration one day). I noticed like Brendan
> that some parameter are configured even if you didn't
> want.
> I edited the autoconf.h but no really changes.

Dan suggests (look at the mailing list archives) that linux-2.3.18.tgz
is what you should use instead of mpc8xx-2.3.10.tgz.  He also suggested
that he might remove the mpc8xx-2.3.10.tgz archive and I think that
would be a good idea if it has problems compiling or has some confusing
elements.  Since it is a bleeding edge release you must expect
problems.  I have reverted back to the embedded-2.2.5.tgz archive for my
port.  It compiles fine with the right options.  I would probably
recommend the 2.2.5 stuff for first timers (like me) as this is the most
stable version and there are apparently lots of MPC8xx boards using this
kernel.


> According to Dan, it seems to be tooo difficult to
> cross compile on a host pentium machine (I begin to be
> mainly agree with him),so I'm going to obtain a
> powermac station.
>
> However I would like to know before if someone has
> already succeeded to build a zImage or zImage.initrd
> configured for a MPC860 MBX board on a host pentium
> (II 400) station?

I have had no problems compiling the kernel with the x86->ppc
cross-compiler, though I would still love to have a PowerPC machine
instead of an x86.  The only problems I had have been choosing the right
configuration options.  Once you have sorted this out you should be
fine.  Have you installed a x86-ppc cross-compiler ?  I can help you if
you are having problems with it (building the compiler or using it to
compile the kernel).  Note that any questions on building an i86->ppc
cross-compiler should be sent to the crossgcc mailing list.  See
http://www.objsw.com for FAQ and subscription details.  I am using
egcs-1.1.2 and there is a prebuilt egcs-1.1.1 cross-compiler available
from the LinuxPPC web pages.

Brendan Simon.

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

  parent reply	other threads:[~1999-09-24  0:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-23 15:05 Questions on the MPC8xx-2.3.10 realease sébastien tadéoni
1999-09-23 17:31 ` Scott Wood
1999-09-24  0:37 ` Brendan Simon [this message]
1999-09-27 10:17 ` Marcus Sundberg

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=37EAC7E0.3AE82656@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sebastien_tadeoni@yahoo.fr \
    /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.