From: "Dave Airlie" <airlied@parthus.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] building arm ROM without GDB stubs
Date: Mon, 15 Jan 2001 03:55:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0101151155570.29987-100000@platinum.limerick.sslinc.com> (raw)
Using Cygwin / Windows Configtool I can genearate an .ecc file with no
conflicts but when I compile I get:
rm-elf-gcc -c -I//D/ecos/fj1_install/include
-I//R/devel/ecos-010112/packages/hal/common/current
-I//R/devel/ecos-010112/packages/hal/common/current/src
-I//R/devel/ecos-010112/packages/hal/common/current/tests
-I. -I//R/devel/ecos-010112/packages/hal/common/current/src/
-mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -Wp,-MD,src/hal_if.tmp -o
src/hal_common_hal_if.o
//R/devel/ecos-010112/packages/hal/common/current/src/hal_if.c
//R/devel/ecos-010112/packages/hal/common/current/src/hal_if.c:142: #error
" no RESET_ENTRY"
make[1]: *** [src/hal_if.o.d] Error 1
make[1]: Leaving directory `/d/ecos/fj1_build/hal/common/current'
make: *** [build] Error 2
If I add GDB stubs in HAL to my ROM image I can build a library
successfully, I am sure I've done this before has something changed?
I'm using snapshot from 12 January...
Dave.
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com
next reply other threads:[~2001-01-15 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 3:55 Dave Airlie [this message]
2001-01-15 5:40 ` Jesper Skov
2001-01-15 6:07 ` Dave Airlie
2001-01-15 7:10 ` Jesper Skov
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=Pine.LNX.4.21.0101151155570.29987-100000@platinum.limerick.sslinc.com \
--to=airlied@parthus.com \
--cc=ecos-discuss@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).