From: Fonin.external@infineon.com
To: ecos-maintainers@sources.redhat.com
Subject: Compiling questions
Date: Wed, 08 Oct 2003 09:03:00 -0000 [thread overview]
Message-ID: <855134C63EDB28488B2D815FE6BEEE61587826@mucse003.eu.infineon.com> (raw)
Dear maintainers
Currently we evaluates different operating systems and your system is quite interesting for us. I would be thankful if you ask me the follow question:
We installed the version 2-.0b1 of eCos software. During the compilation of eCos for the ARM architecture the following error of makefile was occurred:
make -r -C hal/arm/arch/v2_0b1 arm.inc
make[1]: Entering directory `/ecos-c/ecos-2.0b1/examples/ex1_build/hal/arm/arch/v2_0b1'
arm-elf-gcc -mcpu=arm7tdmi -mno-short-load-words -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -I/ecos-c/ecos-2.0b1/examples/ex1_install/include -I/ecos-c/ecos-2.0b1/packages/hal/arm/arch/v2_0b1 -I/ecos-c/ecos-2.0b1/packages/hal/arm/arch/v2_0b1/src -I/ecos-c/ecos-2.0b1/packages/hal/arm/arch/v2_0b1/tests -I. -Wp,-MD,arm.tmp -o hal_mk_defs.tmp -S /ecos-c/ecos-2.0b1/packages/hal/arm/arch/v2_0b1/src/hal_mk_defs.c
make[1]: Leaving directory `/ecos-c/ecos-2.0b1/examples/ex1_build/hal/arm/arch/v2_0b1'
arm-elf-gcc.exe: /ecos-c/ecos-2.0b1/packages/hal/arm/arch/v2_0b1/src/hal_mk_defs.c: No such file or directory
arm-elf-gcc.exe: no input files
make[1]: *** [arm.inc] Error 1
make: *** [build] Error 2
make: Leaving directory `/ecos-c/ecos-2.0b1/examples/ex1_build'
The arm-gcc-elf.exe has been correctly install and path to it is in the PATH variable.
What is wrong?
Thank you
Fonin Yuri
Infineon tech.
next reply other threads:[~2003-10-08 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 9:03 Fonin.external [this message]
2003-10-08 9:35 ` John Dallaway
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=855134C63EDB28488B2D815FE6BEEE61587826@mucse003.eu.infineon.com \
--to=fonin.external@infineon.com \
--cc=ecos-maintainers@sources.redhat.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).