This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[eCos v1.3.1/net] Old-style path convention results in Run Tests error


Hi,

Let me quote, if I may, an older message which describes my problem,
too:

---------- Begin Quoted Message ----------
From: max rtos <maxrtos at yahoo dot com>
To: ecos <ecos-discuss at sources dot redhat dot com>
Date: Thu, 28 Feb 2002 21:18:03 -0800 (PST)
Subject: [ECOS] run tests problems

I have built library and tests for a pc target.
Tools->Run Tests->choose one of tests->run
At output I got:

//C/CYGWIN/WK/PC386/PCTARG~1/TESTS/HAL/COMMON/CURRENT/TESTS/BASIC
.EXE:
No such host or network path.
(gdb) set height 0
(gdb) set remotedebug 0
Warning: command 'set remotedebug' is deprecated.
Use 'set debug remote'.com2comco

It seems it does not know where is //C. I got similar
message when I first time build tests. After I update
my ecos configuration tool, it went away. Now I have
the version 1.3.net on win95.
Thanks
---------- End Quoted Message ----------

The only answer came from Jonathan Larmour:

---------- Begin Jonathan Larmour's answer ----------
From: Jonathan Larmour <jlarmour at redhat dot com>
To: max rtos <maxrtos at yahoo dot com>
Cc: ecos <ecos-discuss at sources dot redhat dot com>
Date: Fri, 01 Mar 2002 20:09:36 +0000
Subject: Re: [ECOS] run tests problems

Evidently there is still some bug lurking in the config tool that it
uses the //x notation for drive paths when it shouldn't. If
you're enterprising, you can try fixing it by checking out the sources
in host/tools/configtool.
Or (more likely) you should submit it as a bug in bugzilla:
http://sources.redhat.com/ecos/problemreport.html
---------- End Jonathan Larmour's answer ----------

One year later, is this the definitive answer to this problem? Is
there anything else a beginner could do to resolve this issue, or is
it a lost cause? Should we just abandon v1.3.1/net altogether?

One of the proposed solutions was to switch to an older version of
Cygwin, but I'm not sure if such a version is still circulating around
the Internet.

Being unfamiliar with CVS, I chose to download eCos v2 full beta
snapshot from ecoscentric.com. It's impressive, but I'm not interested
in the source code at this very moment, since I wouldn't know how to
compile it -- I don't have the knowledge for that.

I could get the company I'm working for to pre-order eCos 2.0 Beta
CDROM. Would that be the best thing to do?

I appreciate all the advice/suggestions you can give me.

Thank you.

--
Cabeze de Vaca



_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail



-- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]