From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] #error " no RESET_ENTRY" ??
Date: Tue, 09 Jan 2001 14:48:00 -0000 [thread overview]
Message-ID: <20010109165157.A16129@visi.com> (raw)
I'm trying to impliment virtual vector support in my HAL, but I
can't get it to build. I am getting the following error
/opt/ecos/ecos-cvs/ecos/packages/hal/common/current/src/hal_if.c:143: #error " no RESET_ENTRY"
The problem seems to be that my plf_stubs.h file only defines a
reset entry point if CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is
defined (because that's what the edb7xxx HAL does it).
However, hal_if.c demands that a reset entry point be defined
if CYGPRI_HAL_IMPLEMENTS_IF_SERVICES is defined.
Does CYGPRI_HAL_IMPLEMENTS_IF_SERVICES imply
CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS?
At this point what I'm attempting is
* I don't want GDB stubs in my eCos application.
* I want to fill in the virtual vector table.
* I don't want to do diagnostic I/O via the virtial vector table.
My current configuration is
#undef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
#define CYGSEM_HAL_VIRTUAL_VECTOR_SUPPORT
#define CYGPRI_HAL_IMPLEMENTS_IF_SERVICES
#undef CYGSEM_HAL_VIRTUAL_VECTOR_DIAG
Which means (I think)
Don't include GDB stubs in eCos.
HAL does support virtual vector table.
HAL fills in virtual vector table.
HAL does not call diagnostic I/O routines via virtual vector table.
Is that an illegal configuration?
ecosconfig seems happy...
--
Grant Edwards
grante@visi.com
next reply other threads:[~2001-01-09 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 14:48 Grant Edwards [this message]
2001-01-09 16:36 ` Jonathan Larmour
2001-01-10 7:46 ` Grant Edwards
2001-01-10 8:40 ` Jonathan Larmour
2001-01-10 9:28 ` Grant Edwards
2001-01-10 0:11 ` Jesper Skov
2001-01-10 7:32 ` Grant Edwards
2001-01-10 10:08 ` 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=20010109165157.A16129@visi.com \
--to=grante@visi.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).