From: Bob Brusa <bob.brusa@gmail.com>
To: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] library build error using arm-eabi tools 4.6.3-20120623
Date: Mon, 28 Jan 2013 15:23:00 -0000 [thread overview]
Message-ID: <510697DE.5060505@gmail.com> (raw)
Hi,
when building the library with Configtool I get an error:
...cut
make[1]: Entering directory
`/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_build/hal/arm/arch/current'
arm-eabi-gcc -finline-limit=7000 -Os -Wall -Wpointer-arith
-Wstrict-prototypes -Wundef -Wno-write-strings -mcpu=arm7tdmi -g
-ffunction-sections -fdata-sections -fno-exceptions
-mno-thumb-interwork
-I/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_install/include
-I/opt/ecos/packages/hal/arm/arch/current
-I/opt/ecos/packages/hal/arm/arch/current/src
-I/opt/ecos/packages/hal/arm/arch/current/tests -I. -Wp,-MD,arm.tmp -o
hal_mk_defs.tmp -S /opt/ecos/packages/hal/arm/arch/current/src/hal_mk_defs.c
fgrep .equ hal_mk_defs.tmp | sed s/#// > arm.inc
fgrep: hal_mk_defs.tmp: No such file or directory
makefile:37: recipe for target `arm.inc' failed
tail: cannot open `arm.tmp' for reading: No such file or directory
make[1]: Leaving directory
`/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_build/hal/arm/arch/current'
make[1]: *** [arm.inc] Error 1
makefile:15: recipe for target `build' failed
make: *** [build] Error 2
make: Leaving directory `/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_build'
When generating the library using the old toolchain that came with
eCos3.0, this problem does not exist.
Does anyone have good advice?
Thanks and best regards - Bob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2013-01-28 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 15:23 Bob Brusa [this message]
2013-01-28 19:29 ` [ECOS] " 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=510697DE.5060505@gmail.com \
--to=bob.brusa@gmail.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).