From: Jonathan Larmour <jlarmour@redhat.com>
To: David Geng <deli.geng@ncl.ac.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Can NOT build tests
Date: Mon, 30 Oct 2000 16:28:00 -0000 [thread overview]
Message-ID: <39FE1242.DFDE861F@redhat.com> (raw)
In-Reply-To: <000d01c04258$6d43f7a0$5210f080@ncl.ac.uk>
David Geng wrote:
>
> So I was wondering what's wrong with the heaps.cxx, and what is the _heap1?
> I feel heap1 is a memory region which's found in the eCos memory layout,
> right? BTW, I'm using the repository from CVS with eCos 1.3.1.1.
Have you changed your memory layout? If so, you'll need to use an updated
Configuration tool. If you use the default memory layout this problem
should go away.... except of course your memory layout will probably not be
right for what you want :-). I intend to put a new config tool up tomorrow
for FTP. Watch this space.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-10-30 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 2:03 David Geng
2000-10-30 16:28 ` Jonathan Larmour [this message]
2000-10-31 15:38 ` Jonathan Larmour
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=39FE1242.DFDE861F@redhat.com \
--to=jlarmour@redhat.com \
--cc=deli.geng@ncl.ac.uk \
--cc=ecos-discuss@sourceware.cygnus.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).