public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Mike Arthur" <arth2219@gmail.com>
To: "ANILA SOOMRO" <dranne27@hotmail.com>
Cc: "Antoine Zen-Ruffinen" <antoine.zen@gmail.com>,
	 	"eCos Mailing List" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] target.ld error
Date: Tue, 22 Jan 2008 18:27:00 -0000	[thread overview]
Message-ID: <2a3305fe0801221027o7553ed10of121278cb931604f@mail.gmail.com> (raw)
In-Reply-To: <BLU111-W31E456B5C5005B5B2EEA60D83E0@phx.gbl>

> I choose the PowerPC simulator target and build it.

Did you build your kernel library with the PowerPC compiler or your
native compiler (gcc) ?  What's the value of
CYGBLD_GLOBAL_COMMAND_PREFIX in your kernel configuration?

If you don't know how to find the value of CYGBLD_GLOBAL_COMMAND_PREFIX:
1.) Select Edit -> Find... in the ConfigTool.  A find dialog box should pop up.
2.) Set the "Search In" field to "Macro Names"
3.) Search for CYGBLD_GLOBAL_COMMAND_PREFIX

It should be "powerpc-eabi-".  If it is, then you've been compiling
with the powerpc-eabi-gcc compiler that's on your Windows machine.
That's a good thing!


> My installation or build directory is c:\eCos-Work\PPC_install.
> After doing this and following the user guide, I try to compile the hello.c example.
> When I use the powerpc-eabi-gcc command, I get this error: bash: powerpc-eabi-gcc: command not found.

This means that either you don't have have the powerpc-eabi-gcc
compiler, or (more likely) that the command's path is not in your PATH
environment variable.

Usually the eCos cross compilers reside in C:\cygwin\opt\gnutools.  My
powerpc-eabi-gcc resides in:

C:\cygwin\opt\gnutools\powerpc-eabi\bin\powerpc-eabi-gcc

Make sure to use a cygwin formatted path (i.e. /cygdrive/c/...).

Hope this helps,
Mike

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-01-22 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BLU111-W317191F97CB76ED8313455D84B0@phx.gbl>
2008-01-11 10:32 ` Antoine Zen-Ruffinen
     [not found]   ` <BLU111-W1105E0211A6739699F4AA5D84B0@phx.gbl>
2008-01-11 12:31     ` Antoine Zen-Ruffinen
2008-01-14 12:51       ` Antoine Zen-Ruffinen
2008-01-22  6:40         ` ANILA SOOMRO
2008-01-22 18:27           ` Mike Arthur [this message]
2008-01-23  6:32             ` ANILA SOOMRO
2008-01-11  8:01 ANILA SOOMRO
2008-01-11  8:52 ` Antoine Zen-Ruffinen
2008-01-11 10:43 ` Alexandre

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=2a3305fe0801221027o7553ed10of121278cb931604f@mail.gmail.com \
    --to=arth2219@gmail.com \
    --cc=antoine.zen@gmail.com \
    --cc=dranne27@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).