linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gerlach <gerlach@kip.uni-heidelberg.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Newbie on embedded linux on PPC: error: cannot find boot.o
Date: Wed, 05 Sep 2007 10:17:03 +0200	[thread overview]
Message-ID: <46DE65FF.3040202@kip.uni-heidelberg.de> (raw)
In-Reply-To: <fa686aa40709040747j503a2054x27ba2b8146a93ff8@mail.gmail.com>

Grant Likely wrote:
> On 9/4/07, Thomas Gerlach <gerlach@kip.uni-heidelberg.de> wrote:
>   
>> hi folks,
>>
>>
>> my name is thomas trying to make embedded linux run on a powerpc, but we've got special boards here, although we use a xilinx virtex4 fpga...
>>
>> as you said in the nabble-thread (see subject), i set up edk9.1 software platform settings und ran libgen to get the xparameters* files. i copied those bsp files into the kernel tree (i use your kernel linux-2.6-virtex from git.secretlabs.ca/git). after configuring the kernel settigs, i try
>>
>> $ make ARCH=ppc CROSS_COMPILE=powerpc-eabi-
>>     
>
> You should be using a Linux cross compiler, not powerpc-eabi-.  The
> Xilinx cross compiler will not work to compile Linux kernels.
>
> You can build yourself a cross compiler using 'crosstool':
> http://www.kegel.org/crosstool.
>
> Alternately, you can download ELDK:
> http://www.denx.de/wiki/view/DULG/ELDKAvailability
>
> Cheers,
> g.
>
>   

hi,
thank you much for this hint. this was the last thing i thought of... ;)

so long, keep on cross-compiling! :)

regards,
thomas

  reply	other threads:[~2007-09-05  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 13:48 Newbie on embedded linux on PPC: error: cannot find boot.o Thomas Gerlach
2007-09-04 14:47 ` Grant Likely
2007-09-05  8:17   ` Thomas Gerlach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-04 14:03 Thomas Gerlach
2007-09-04 21:33 ` Wolfgang Reissnegger
2007-09-05  8:18   ` Thomas Gerlach
2007-09-06 18:39   ` Stephen Neuendorffer

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=46DE65FF.3040202@kip.uni-heidelberg.de \
    --to=gerlach@kip.uni-heidelberg.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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).