public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] #error " no RESET_ENTRY"  ??
Date: Wed, 10 Jan 2001 07:46:00 -0000	[thread overview]
Message-ID: <20010110095023.A23531@visi.com> (raw)
In-Reply-To: <3A5BAE8A.F94A050F@redhat.com>

On Wed, Jan 10, 2001 at 12:36:26AM +0000, Jonathan Larmour wrote:

> > 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).
> 
> It doesn't in current CVS. Perhaps your CVS tree predates virtual vectors
> getting added for the edb7xxx (it was 5th July it got added).

Vitrual vector support is in my snapshot of the edb7xxx
HAL (it's the one after which I'm modelling mine. My CVS tree
is from about a month ago.  The last entry in the ChangeLog is

2000-11-25  Jonathan Larmour  <jlarmour@redhat.com>

        * pkgconf/rules.mak (mlt_headers): Rewrite to work under Solaris,
        and without excessive rebuilds.

Once I get things into a stabe, working state I might try
updating.

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2001-01-10  7:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 14:48 Grant Edwards
2001-01-09 16:36 ` Jonathan Larmour
2001-01-10  7:46   ` Grant Edwards [this message]
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=20010110095023.A23531@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@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).