This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ecosconfig build problem
- From: Bill <wbarber at nsgdata dot com>
- To: Gary Thomas <gary at mlbassoc dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 16 Feb 2005 06:46:35 -0700
- Subject: Re: [ECOS] ecosconfig build problem
- References: <4212BA63.2060502@nsgdata.com> <1108551980.20784.52.camel@hermes>
Gary Thomas wrote:
On Tue, 2005-02-15 at 20:13 -0700, Bill wrote:
Hi, I have several issues related to building a custom redboot system
which need to be resolved. I will start with the easy one.
I have been successfully building a redboot system for a new proprietary
hardware design using a MPC8247 powerquicc2. Due to some problems with
serial ports I decided to build the redboot version of the standard
'motorola vads' config.
Now, no matter what I try I can't build either. When I try to build my
system it tells me I have no rule to build mpc8260.h. I don''t use
mpc8260. When I try to build 'vads' is tells me there is no rule for
mpc82xx.h which is part of my proprietary build, but not vads. vads uses
mpc8260.
The ecos.db file and all cdl files are valid. How can I clean things out
to get rid of this problem?? It is critical because I can't build
anything now.
Work from CVS and start with the 'rattler' platform. The VADS
is not really supported anymore.
Thanks for the tip. It will probably answer some of my other redboot
questions.
I got around the 'catch 22' type build problem late last night by
deleting all files of the form ...a.deps from
packages/hal/powerpc/arch/current.They appeared to be stale for some
reason.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss