linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
To: sébastien tadéoni <sebastien_tadeoni@yahoo.fr>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problem for compiling linux-2.2.5-embedded
Date: Wed, 15 Sep 1999 11:14:53 +1000	[thread overview]
Message-ID: <37DEF30C.EFB188F6@ctam.com.au> (raw)
In-Reply-To: 19990914142953.21439.rocketmail@web601.yahoomail.com


sébastien tadéoni wrote:

> I've some problems with the cross-compilation of the 2.2.5-embedded
> kernel for MPC860 (configure for a MBX card).
>
> ppc_ksyms.c:77:'isa_io_base' undeclared here (not in a fonction)
>
> ppc_ksyms.c:77:'initializer element for '--ksymtab_isa_io_base.value'
> is not constant
>
> In the ppc_ksyms.c I see EXPORT_SYMBOL(isa_io_base) and I don't no what
> it minds.

First join the new linuxppc-embedded mailing list.  This is a ppc-embedded
problem and there is no need to hassle the ppc-users or ppc-developers.

I had these problems too.  It is definately a configuration problem.  I am
using the latest embedded source mpc8xx-2.3.10.tgz but had the same
problems with embedded-2.2.5.  Send your .config file.

Things you should NOT have included are :
- serial support and serial-console support.  I know this sounds wrong but
that's the way it is.
- virtual terminals
- make sure that no network cards are selected.

Brendan Simon.

PS. I think there is a sample configuration file in embedded-notes.txt or
mbx-notes.txt on the ftp site.


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

  reply	other threads:[~1999-09-15  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-14 14:29 Problem for compiling linux-2.2.5-embedded sébastien tadéoni
1999-09-15  1:14 ` Brendan Simon [this message]
1999-09-15  2:21   ` Dan Malek

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=37DEF30C.EFB188F6@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 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).