From: j.d.charlton@ieee.org
To: patrick@softprocess.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Embedded PC SBC
Date: Mon, 10 Jan 2000 15:21:00 -0000 [thread overview]
Message-ID: <200001102321.SAA04319@smtp6.mindspring.com> (raw)
In-Reply-To: <Pine.BSF.4.10.10001070913360.3381-100000@plasticgrape.com>
Patrick and ecos-discuss,
I am forging ahead with the ecos i386-pc build. I think I set
everything up the way Patrick's html files described it starting from
the ecos-1.2.1.tar distribution tree. I am building using RedHat
6.0. I first untarred only the latest file: hal-i386-pc-19991028.tgz
I got the error below. I decided to go back and untar the initial
release (hal-i386-pc-0.1.tar) followed by the second release
(hal-i386-pc-19991022.tgz) and then the final version
(hal-i386-pc-19991028.tgz) just in case it was meant to be done that
way, but I still get the same error when building the gdb stub:
[charlton@marble ecos-i386-stub]$ tclsh ~/cygnus/ecos-1.2.1/packages/pkgconf.tcl \
> --target i386 \
> --platform pc \
> --startup floppy \
> --disable-kernel \
> --disable-uitron \
> --disable-libc \
> --disable-libm \
> --disable-io \
> --disable-io_serial \
> --disable-wallclock \
> --disable-watchdog
pkgconf fatal error: The file /home/charlton/cygnus/ecos-1.2.1/packages/packages \
lists a package CYGPKG_HAL_ARM_CL7211 which should be present in \
/home/charlton/cygnus/ecos-1.2.1/packages/hal/arm/cl7211. This package is missing.
[charlton@marble ecos-i386-stub]$
Any help is appreciated.
--John
On 7 Jan, Patrick O'Grady wrote:
>
>
> Hi, J.D.:
>
> I posted an i386/PC HAL package;
> http://sourceware.cygnus.com/ecos/contrib.html has a pointer to it. The
> last time I updated it was the end of October, so don't be suprised if the
> eCos source code has changed quite a bit--installation might not be as
> straightforward as before. I'm actually planning on updating to the
> current CVS version next week. Look out for a bug somewhere in the mutex
> handling code: I'm sure it's related to the interrupt handler code. Stay
> tuned for that fix. But in the meantime, that package allows you to
> construct a GDB stub on a floppy disk, so you just boot from that and then
> connect to the debugger from COM1. If you have any significant problems,
> just e-mail questions to this list, that way everyone benefits from the
> discussion. Cheers!
>
> -patrick
> patrick@softprocess.com
>
>
next prev parent reply other threads:[~2000-01-10 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 13:05 j.d.charlton
2000-01-07 9:21 ` Patrick O'Grady
2000-01-07 12:09 ` j.d.charlton
2000-01-08 0:04 ` Gary Thomas
2000-01-10 15:21 ` j.d.charlton [this message]
2000-01-10 16:03 ` Gary Thomas
2000-01-10 17:51 ` j.d.charlton
2000-01-14 5:57 ` [ECOS] " Bart Veer
2000-01-14 11:54 ` Patrick O'Grady
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=200001102321.SAA04319@smtp6.mindspring.com \
--to=j.d.charlton@ieee.org \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=patrick@softprocess.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).