public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "David Geng" <deli.geng@ncl.ac.uk>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Can NOT build tests
Date: Mon, 30 Oct 2000 02:03:00 -0000	[thread overview]
Message-ID: <000d01c04258$6d43f7a0$5210f080@ncl.ac.uk> (raw)

Hello,

By now I have setup eCos environment and built GDB stub successfully.
Further step, I want to build some tests to verify the eCos configuration.
But, unfortunately, it's failed. I tried to rebuild it many times, results
were the same. I also tried to build single test program. It's also failed.
The following is an example output:

$ make -C kernel/current tests TESTS=tests/tm_basic
make: Entering directory `/d/eCos386/test_build/kernel/current'
i386-elf-gcc -g -nostdlib -Wl,--gc-sections -Wl,-static -L//D/eCos386/test_i
nstall/lib -Ttarget.ld -o
//D/eCos386/test_install/tests/kernel/current/tests/tm_basic
tests/tm_basic.o
//D/eCos386/test_install/lib/libtarget.a(services_memalloc_common_heaps.o):
In function `global destructors keyed to 49900.cygmem_memalloc_heaps':
/d/eCos386/test_build/services/memalloc/common/current/heaps.cxx:19:
undefined reference to `_heap1'
/d/eCos386/test_build/services/memalloc/common/current/heaps.cxx:19:
undefined reference to `_heap1'
collect2: ld returned 1 exit status
make: *** [//D/eCos386/test_install/tests/kernel/current/tests/tm_basic]
Error 1

make: Leaving directory `/d/eCos386/test_build/kernel/current'

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.

Any one would like to help me? Thank you so much in advance.

Regards

David


             reply	other threads:[~2000-10-30  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30  2:03 David Geng [this message]
2000-10-30 16:28 ` Jonathan Larmour
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='000d01c04258$6d43f7a0$5210f080@ncl.ac.uk' \
    --to=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).