linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scott@broadlink.com>
To: sébastien tadéoni <sebastien_tadeoni@yahoo.fr>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Cross compilation for MPC860
Date: Thu, 16 Sep 1999 18:21:52 +0000	[thread overview]
Message-ID: <37E13540.1A410F5C@broadlink.com> (raw)
In-Reply-To: 19990916125231.12806.rocketmail@web601.yahoomail.com


sébastien tadéoni wrote:
...
> 
> During the make zImage I get the following errors:
> 
> ppc_ksyms.c:71:'isa_io_base' undeclared here (not in a fonction)
> 
> ppc_ksyms.c:71:'initializer element for '--ksymtab_isa_io_base.value'
> is not constant,
> 
> And the same thing with the variable pci_dram_offset.
> 
> Perhaps is there a configuration problem or I didn't install correctly
> the powerpc-linux environment for cross development?
> 

Your cross-compile environment is good for building kernels.  This is a kernel
configuration issue.  I got the same isa_io_base error building on a PowerMac 
(which doesn't have ISA) until I enabled SCSI support (?!?!?).  For my MPC850 build 
I commented out EXPORT_SYMBOL(isa_io_base); and also isa_mem_base and pci_dram_offset
in arch/ppc/kernel/ppc_ksyms.c and I was able to successfully build a kernel without SCSI.
Note that the 2.2.5-embedded kernel compiles in ADB support whether you configured for
it or not (correct me if I'm wrong, but that has been my experience so far), so I 
commented out L_OBJS and LX_OBJS in drivers/macintosh/Makefile and it builds without ADB.  

> On top of that the /usr/local/powerpc_linux/include directory is empty
> so that I can't make the ln -s with the include/linux and include/asm
> directories(in my linux sources directory) before I want to build the
> LibC.
> 

Mine is empty too, and I can build kernels fine, but I get lots of errors trying
to build anything else.  Instead of fussing with it (I don't know _why_ the builds 
fail anyway) I got a PowerMac, loaded YellowDog Linux, and all is well :-)

> I will appreciate any suggestions and help  from you on this subject.
> 
> Thanks in advance.
> Have a good day.
> 
> Sébastien.

-- 
+---------------------+----------------------+
|     Scott Wood      |   Systems  Engineer  |
|=====================+======================|
|           BroadLink Communications         |
+--------------------------------------------+

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

  reply	other threads:[~1999-09-16 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-16 12:52 Cross compilation for MPC860 sébastien tadéoni
1999-09-16 18:21 ` Scott Wood [this message]
1999-09-16 23:44   ` Brendan Simon
1999-09-17  0:23 ` Graham Stoney
1999-09-17  1:12   ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
1999-09-21 12:40 sébastien tadéoni

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=37E13540.1A410F5C@broadlink.com \
    --to=scott@broadlink.com \
    --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).