This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: can't get ecosconfig to use "current" version
- From: Grant Edwards <grante at visi dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Tue, 22 May 2007 16:26:26 +0000 (UTC)
- Subject: [ECOS] Re: can't get ecosconfig to use "current" version
- References: <f2uuoh$94u$1@sea.gmane.org>
On 2007-05-22, Grant Edwards <grante@visi.com> wrote:
> If I try to tell ecosconfig to use the current version it
> complains:
>
> $ ecosconfig new dm2 net current
>
> Usage: ecosconfig [ qualifier ... ] [ command ]
> commands are:
> list : list repository contents
> new TARGET [ TEMPLATE [ VERSION ] ] : create a configuration
> target TARGET : change the target hardware
> template TEMPLATE [ VERSION ] : change the template
> [...]
>
> If I leave off the "current", it selects v2_0 (which won't
> configure/build because of conflicts between packages).
>
> So I've got two questions
>
> 1) What would cause ecosconfig to decided it likes v2_0 better
> than current?
Others have apparently run into this and haven't been able to
find an answer either.
> 2) How do I tell it I want current?
This seems to be a known problem:
http://thread.gmane.org/gmane.os.ecos.general/17834/focus=17837
According to the above thread, the bug in command-line parsing
that is rejecting the version specifier has been fixed. But,
I'd still like to know how ecosconfig decides what version it's
going to build by default. I've searched the Users Guide, the
Reference Guide, and the Component Writers Guide, and didn't
find any documentation on ecosconfig other than a few examples.
--
Grant Edwards grante Yow! My BIOLOGICAL ALARM
at CLOCK just went off ... It
visi.com has noiseless DOZE FUNCTION
and full kitchen!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss