[ECOS] RE: libsupc++.a

[ECOS] RE: libsupc++.a

[Koeller, T.]

Martin,

I never quite understood how this (using newlib) is supposed to work,
and that's why I never tried it. If I use newlib to generate the compiler
support libraries like libsupc++, doesn't this mean I will have to link
all my applications with newlib? And if I do, won't there be clashes between
newlib and the ecos-provided ISO C library functions? Am I wrong to assume
that I cannot use just the newlib headers without using the actual library?

I am cc'ing this to the ecos-discuss mailing list, as this is a question of
general interest. Hope that you, or anyone else, can shed some more light on
this topic that has puzzled me for long.

tk


> -----Original Message-----
> From: Martin Buck [mailto:martin.buck@ascom.ch]
> Sent: Monday, June 17, 2002 4:49 PM
> To: ecos-patches@sources.redhat.com; Koeller, T.
> Subject: Re: libsupc++.a
> 
> 
> "Koeller, T." wrote:
> > You can only build a cross gcc for ecos by doing a 'make 
> all-gcc'. This
> > does not build libsupc++.a, a 'make all' would be required 
> to achieve
> > this, which is impossible to do as there is no target C 
> library at this
> > point.
> 
> You don't need "make all", "make all-gcc all-target-libstdc++-v3" is
> sufficient. For this to work, you have to compile with newlib (and you
> have to #define _GLIBCPP_HAVE_UNISTD_H when compiling
> libstdc++-v3/libsupc++/pure.cc - the configure script seems 
> to get this
> one wrong in recent gccs). BTW, compiling with newlib is what RedHat
> suggests[1] and is what is done in toolchains they ship to their
> customers.
> 
> [1] http://sources.redhat.com/ml/ecos-discuss/2001-10/msg00274.html
> 
> > And then, functions in libsupc++.a should use the mechanisms
> > provided by the target system directly for efficiency. Take 
> as an example
> > the one function I implemented, __cxa_pure_virtual(). Its 
> purpose is to
> > abort a program if it happens to call a pure virtual 
> function. The version
> > that comes with gcc (or, more precisely, with libstdc++) 
> does this by
> > calling
> > std::terminate(), so it requires the standard C++ library.
> 
> std::terminate is part of libsupc++ as well. AFAIK, there are no
> dependencies on libstdc++ in libsupc++. If there were any, I 
> would call
> this a bug.
> 
> > For an embedded
> > system it is clearly preferable to map this simple 
> funtionality directly to
> > the ecos-provided mechanisms, CYG_FAIL() in this case.
> > 
> > Providing ecos-specific implementations for these functions 
> also has the
> > additional benefit of being able to add ecos-style 
> asertions, tracing and
> > so on.
> 
> That's right, but it has the huge drawback of messing around with an
> internal compiler-API that can change without warning. Plus, 
> you'll have
> to implement a lot of stuff from libsupc++ to be more-or-less ISO C++
> compliant.
> 
> Martin
> 

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

[ECOS] Re: libsupc++.a

[Martin Buck]

"Koeller, T." wrote:
> I never quite understood how this (using newlib) is supposed to work,
> and that's why I never tried it.

To be honest, neither do I, but I somehow managed to get it working. :-)

> If I use newlib to generate the compiler
> support libraries like libsupc++, doesn't this mean I will have to link
> all my applications with newlib?

In theory, yes. But basically, you just use newlib's header files to
provide declarations for the few libc functions libsupc++ wants to use.
Newlib (in contrast to GNU libc, for example, which uses some magic
inline code) seems to be a more-or-less straightforward libc
implementation, so you end up with with a few undefined symbols in
libsupc++ that happen to be provided by the eCos libc in a compatible
way, so you can link the whole stuff together and it just works. This
wouldn't work if libsupc++ would to things like "sizeof(FILE)" which
would most likely give different results with newlib/eCos libc, but I
guess the libsupc++ authors knew about this and took it into account.

The correct solution of course would be to compile libsupc++ against the
header files of the libc you want to link it against, but then the
libsupc++ authors would have to deal with all the possible libc's out
there. And as long as the interface between libsupc++ and libc is lean
enough (libsupc++ currently only needs malloc(), free(), memset() and
write()), I guess we can live with the current "good enough" solution.

Oh, and as I mentioned in my previous e-mail: The configure scripts in
my current toolchain (which seems to be a close relative of gcc 3.1)
seem to get a bit confused by newlib. So you might have to add a
"#define _GLIBCPP_HAVE_UNISTD_H" to the beginning
libstdc++-v3/libsupc++/pure.cc if you get undefined symbols when linking
applications using virtual functions. Apart from this, everything else
works automagically if you unpack newlib to the subdirectory "newlib" in
the toolchain sources and configure the toolchain with "--with-newlib".
As I said, this is exactly the way toolchains provided by RedHat to
their customers are configured.

HTH,
Martin

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

[ECOS] Still have some problem about install net-1_01b1.epk

[peter_ku]

Dear All,

need your help.

I try to install net-1.0b1.epk
1. cp gzip.exe gunzip.exe
2. ./ecosadmin.tcl add net-1.0b1.epk

everything is Ok, then I have the following tree

/packages/net/tcpip/current  	(the orignal one)
/packages/net/tcpip/v1_0b1   	 (the new one)

/packages/net/drivers/eth/common/current	 (the original one)
/packages/net/drivers/eth/common/v1_0b1  	(the new one)
/packages/net/drivers/eth/edb7xxx		(the new one)
/packages/net/drivers/eth/quicc		(the new one)


Start to launch ecos configuration tools 1.3.net

There is one warning message:
ecos.db, package CYGPKG_NET_ETH_DRIVERS: warning Version subdirectory `current' does not have a CDL script `eth_drivers.cdl'.

Any suggestion?

Then I ignore the warning. choose Build/template : ARM Evaluator 7T ,  packages : net

There are some Resolve Conflicts message.

Then I press "continue", choose Build/Packages : there is option in the "Networking" item (current, v1_0b1)
I choose v1_0b1. right ?

Here I have another question , there is one "Common ethernet support" item in the "use these packages"(the version is current), and there is another in the "available packages"(the version is empty ,I believe this is the CYGPKG_NET_ETH_DRIVERS I mention earlier)

Should I remove the current one and add the empty-version one ? 

Ok , no matter what I choose , start to build Library , then error.

Here is the error message. Any one tell me the mistake I made??

/ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fd.cxx
In file included from /ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fio.h:65,
                 from /ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fd.cxx:55:
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:117: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:117: parse error before `)'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:118: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:118: parse error before `)'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:120: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:120: parse error before `*'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:122: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:122: parse error before `*'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:125: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:125: parse error before `*'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:127: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:127: parse error before `)'
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:131: type specifier omitted for parameter
/ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:131: parse error before `*'
make[1]: *** [src/fd.o.d] Error 1
make[1]: Leaving directory `/ecos-c/ecos-test/NET-3_build/io/fileio/current'
make: *** [build] Error 2
make: Leaving directory `/ecos-c/ecos-test/NET-3_build'



Thanks a lot for everyone's support.

Peter

Re: [ECOS] Still have some problem about install net-1_01b1.epk

[Gary Thomas]

On Thu, 2002-06-20 at 04:15, peter_ku wrote:
> Dear All,
> 
> need your help.
> 
> I try to install net-1.0b1.epk
> 1. cp gzip.exe gunzip.exe
> 2. ./ecosadmin.tcl add net-1.0b1.epk
> 
> everything is Ok, then I have the following tree
> 
> /packages/net/tcpip/current  	(the orignal one)
> /packages/net/tcpip/v1_0b1   	 (the new one)
> 
> /packages/net/drivers/eth/common/current	 (the original one)
> /packages/net/drivers/eth/common/v1_0b1  	(the new one)
> /packages/net/drivers/eth/edb7xxx		(the new one)
> /packages/net/drivers/eth/quicc		(the new one)
> 
> 
> Start to launch ecos configuration tools 1.3.net
> 
> There is one warning message:
> ecos.db, package CYGPKG_NET_ETH_DRIVERS: warning Version subdirectory `current' does not have a CDL script `eth_drivers.cdl'.
> 
> Any suggestion?

Use anonymous CVS or a snapshot - this stuff you are trying to use is
so old that you'll only have problems and no one will be able to help.

> 
> Then I ignore the warning. choose Build/template : ARM Evaluator 7T ,  packages : net
> 
> There are some Resolve Conflicts message.
> 
> Then I press "continue", choose Build/Packages : there is option in the "Networking" item (current, v1_0b1)
> I choose v1_0b1. right ?
> 
> Here I have another question , there is one "Common ethernet support" item in the "use these packages"(the version is current), and there is another in the "available packages"(the version is empty ,I believe this is the CYGPKG_NET_ETH_DRIVERS I mention earlier)
> 
> Should I remove the current one and add the empty-version one ? 
> 
> Ok , no matter what I choose , start to build Library , then error.
> 
> Here is the error message. Any one tell me the mistake I made??
> 
> /ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fd.cxx
> In file included from /ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fio.h:65,
>                  from /ecos-c/eCos-cvs/ecos-net-1.0b1/ecos/packages/io/fileio/current/src/fd.cxx:55:
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:117: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:117: parse error before `)'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:118: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:118: parse error before `)'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:120: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:120: parse error before `*'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:122: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:122: parse error before `*'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:125: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:125: parse error before `*'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:127: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:127: parse error before `)'
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:131: type specifier omitted for parameter
> /ecos-c/ecos-test/NET-3_install/include/cyg/fileio/sockio.h:131: parse error before `*'
> make[1]: *** [src/fd.o.d] Error 1
> make[1]: Leaving directory `/ecos-c/ecos-test/NET-3_build/io/fileio/current'
> make: *** [build] Error 2
> make: Leaving directory `/ecos-c/ecos-test/NET-3_build'
> 
> 
> 
> Thanks a lot for everyone's support.
> 
> Peter



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

[ECOS]something unclear about CVS

[peter_ku]

Hello,

I should use the CVS earlier!! thanks a lot, Gary.
After I use CVS , I have something unclear.

1. ecos / net /  snmp ??
 After I execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos"
, there is a /pckages/net folder in my directly

Why should I continue to execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos" ? I see this still update the /packages/net.
what is the difference between this two net?

2. After all update finished (ecos, net , snmp), how do I know which version I use currently? Use the ConfigTool, the version is always "current"
I know I can check ChangeLog, but each sub folder have their own ChangeLog file, is that the only way to check?


Best Regards,
Peter

Re: [ECOS]something unclear about CVS

[Gary Thomas]

On Sat, 2002-06-22 at 02:50, peter_ku wrote:
> Hello,
> 
> I should use the CVS earlier!! thanks a lot, Gary.
> After I use CVS , I have something unclear.
> 
> 1. ecos / net /  snmp ??
>  After I execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos"
> , there is a /pckages/net folder in my directly
> 
> Why should I continue to execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos" ? I see this still update the /packages/net.
> what is the difference between this two net?
> 

Your question isn't very clear (I don't see any difference between the
two commands).  The important thing is to let CVS update the whole tree,
which is significant - some 6000 files!. 

> 2. After all update finished (ecos, net , snmp), how do I know which version I use currently? Use the ConfigTool, the version is always "current"
> I know I can check ChangeLog, but each sub folder have their own ChangeLog file, is that the only way to check?

Version "numbers" are a bit confusing here.  eCos was designed to have
stabilized "releases" in which the "current" directories were renamed
to indicate the version.   In this way, a single source tree could 
contain multiple versions of eCos.  However, at this time, the only
version available is the most current (hence the name) from CVS.

You can get version and history information for any file in the 
repository using CVS commands.  Just try this on a file:
  % cvs log <file>


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

RE: [ECOS]something unclear about CVS

[peter_ku]

Hello Gary,

The document says

cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P net
cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp

After I execute the first step: cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
I found everything is in my installed folder, include package/net and package/net/snmp , it looks like NET and SNMP has already installed.
Why I still execute the next two step? 
for example : I see cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp still update the SNMP. 

that is my question , thank you for your help.


Peter



-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Gary Thomas
Sent: Saturday, June 22, 2002 8:32 PM
To: peter_ku
Cc: 'eCos Discussion'
Subject: Re: [ECOS]something unclear about CVS


On Sat, 2002-06-22 at 02:50, peter_ku wrote:
> Hello,
> 
> I should use the CVS earlier!! thanks a lot, Gary.
> After I use CVS , I have something unclear.
> 
> 1. ecos / net /  snmp ??
>  After I execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos"
> , there is a /pckages/net folder in my directly
> 
> Why should I continue to execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos" ? I see this still update the /packages/net.
> what is the difference between this two net?
> 

Your question isn't very clear (I don't see any difference between the
two commands).  The important thing is to let CVS update the whole tree,
which is significant - some 6000 files!. 

> 2. After all update finished (ecos, net , snmp), how do I know which version I use currently? Use the ConfigTool, the version is always "current"
> I know I can check ChangeLog, but each sub folder have their own ChangeLog file, is that the only way to check?

Version "numbers" are a bit confusing here.  eCos was designed to have
stabilized "releases" in which the "current" directories were renamed
to indicate the version.   In this way, a single source tree could 
contain multiple versions of eCos.  However, at this time, the only
version available is the most current (hence the name) from CVS.

You can get version and history information for any file in the 
repository using CVS commands.  Just try this on a file:
  % cvs log <file>


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

RE: [ECOS]something unclear about CVS

[Gary Thomas]

[-- Attachment #1: Type: text/plain, Size: 2986 bytes --]

On Sun, 2002-06-23 at 19:41, peter_ku wrote:
> Hello Gary,
> 
> The document says
> 
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P net
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp
> 
> After I execute the first step: cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
> I found everything is in my installed folder, include package/net and package/net/snmp , it looks like NET and SNMP has already installed.
> Why I still execute the next two step? 
> for example : I see cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp still update the SNMP. 
> 
> that is my question , thank you for your help.
> 

No problem, it's just old documentation.  With the v2.0(alpha), we've
merged in the "net" and "snmp" packages with the mainline sources.

You're probably set to go.

> 
> Peter
> 
> 
> 
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Gary Thomas
> Sent: Saturday, June 22, 2002 8:32 PM
> To: peter_ku
> Cc: 'eCos Discussion'
> Subject: Re: [ECOS]something unclear about CVS
> 
> 
> On Sat, 2002-06-22 at 02:50, peter_ku wrote:
> > Hello,
> > 
> > I should use the CVS earlier!! thanks a lot, Gary.
> > After I use CVS , I have something unclear.
> > 
> > 1. ecos / net /  snmp ??
> >  After I execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos"
> > , there is a /pckages/net folder in my directly
> > 
> > Why should I continue to execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos" ? I see this still update the /packages/net.
> > what is the difference between this two net?
> > 
> 
> Your question isn't very clear (I don't see any difference between the
> two commands).  The important thing is to let CVS update the whole tree,
> which is significant - some 6000 files!. 
> 
> > 2. After all update finished (ecos, net , snmp), how do I know which version I use currently? Use the ConfigTool, the version is always "current"
> > I know I can check ChangeLog, but each sub folder have their own ChangeLog file, is that the only way to check?
> 
> Version "numbers" are a bit confusing here.  eCos was designed to have
> stabilized "releases" in which the "current" directories were renamed
> to indicate the version.   In this way, a single source tree could 
> contain multiple versions of eCos.  However, at this time, the only
> version available is the most current (hence the name) from CVS.
> 
> You can get version and history information for any file in the 
> repository using CVS commands.  Just try this on a file:
>   % cvs log <file>
> 
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

RE: [ECOS]something unclear about CVS

[peter_ku]

Hello,

1. cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos

2. cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -r last-rhepl -P ecos

what is the difference between these two?

If I update the code using first item, am I use ecos2.0 now?

It really confuse me. thanks a lot for your help.

Peter



-----Original Message-----
From: Gary Thomas [mailto:gary@chez-thomas.org]
Sent: Monday, June 24, 2002 8:31 PM
To: peter_ku
Cc: 'eCos Discussion'
Subject: RE: [ECOS]something unclear about CVS


On Sun, 2002-06-23 at 19:41, peter_ku wrote:
> Hello Gary,
> 
> The document says
> 
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P net
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp
> 
> After I execute the first step: cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
> I found everything is in my installed folder, include package/net and package/net/snmp , it looks like NET and SNMP has already installed.
> Why I still execute the next two step? 
> for example : I see cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P snmp still update the SNMP. 
> 
> that is my question , thank you for your help.
> 

No problem, it's just old documentation.  With the v2.0(alpha), we've
merged in the "net" and "snmp" packages with the mainline sources.

You're probably set to go.

> 
> Peter
> 
> 
> 
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Gary Thomas
> Sent: Saturday, June 22, 2002 8:32 PM
> To: peter_ku
> Cc: 'eCos Discussion'
> Subject: Re: [ECOS]something unclear about CVS
> 
> 
> On Sat, 2002-06-22 at 02:50, peter_ku wrote:
> > Hello,
> > 
> > I should use the CVS earlier!! thanks a lot, Gary.
> > After I use CVS , I have something unclear.
> > 
> > 1. ecos / net /  snmp ??
> >  After I execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos"
> > , there is a /pckages/net folder in my directly
> > 
> > Why should I continue to execute "cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos" ? I see this still update the /packages/net.
> > what is the difference between this two net?
> > 
> 
> Your question isn't very clear (I don't see any difference between the
> two commands).  The important thing is to let CVS update the whole tree,
> which is significant - some 6000 files!. 
> 
> > 2. After all update finished (ecos, net , snmp), how do I know which version I use currently? Use the ConfigTool, the version is always "current"
> > I know I can check ChangeLog, but each sub folder have their own ChangeLog file, is that the only way to check?
> 
> Version "numbers" are a bit confusing here.  eCos was designed to have
> stabilized "releases" in which the "current" directories were renamed
> to indicate the version.   In this way, a single source tree could 
> contain multiple versions of eCos.  However, at this time, the only
> version available is the most current (hence the name) from CVS.
> 
> You can get version and history information for any file in the 
> repository using CVS commands.  Just try this on a file:
>   % cvs log <file>
> 
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 

Re: [ECOS]something unclear about CVS

[Jani Monoses]

> Hello,
> 
> 1. cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -P ecos
> 
> 2. cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos -z 6 co -r last-rhepl -P ecos
> 
> what is the difference between these two?
> 
> If I update the code using first item, am I use ecos2.0 now?
yes the first is for ecos2.0 alpha while the second is for the latest non-GPL version 

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