From: Jonathan Larmour <jlarmour@redhat.com>
To: Piteir <piter197@yahoo.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] fail to compile using GCC
Date: Tue, 29 May 2001 10:23:00 -0000 [thread overview]
Message-ID: <3B13DB15.EEA45721@redhat.com> (raw)
In-Reply-To: <20010529085941.99261.qmail@web12301.mail.yahoo.com>
Piteir wrote:
> I try to compile using:
> arm-elf-gcc -g -o hello.exe -I/c/usr/include hello.c
> -L/c/usr/lib -T/usr/lib/target.ld -nostdlib
>
> but got error message that cannot find "target.ld"
> file, I have tried to find it and still cann't find
> it.
/usr/lib isn't the right path (nor is /c/usr/include nor /c/usr/lib). You
should be pointing at the eCos "install" directory which you would have
built from within the configuration tool.
> -is it possible that something wrong when I built the
> ARM development tools for windows? or this is another
> kind of problem?
>
> -also I got confused because the real syntax example
> for compiling is like:
> arm-elf-gcc -g -o 'filename'.exe -IINSTALL_DIR.
> what INSTALL_DIR here supposed to be, the cygwin or
> eCOS dir?
Your eCos install directory.
> -I also try to build the tests from eCOS configuration
> tools but fail to run that, I got warning on "set
> remotedebug"
You can ignore this warning.
> and some errors so I use cywin to run the
> tes and success, is the anyone know how to fix this so
> can be run in eCOS configuration Tool.
You'll have to be more specific about the errors.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-05-29 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 1:59 Piteir
2001-05-29 10:23 ` Jonathan Larmour [this message]
2001-05-29 21:36 ` Piteir
2001-05-30 8:33 ` Jonathan Larmour
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=3B13DB15.EEA45721@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=piter197@yahoo.com \
/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).