Re: [ECOS] Problem Installing CVS eCos

Re: [ECOS] Problem Installing CVS eCos

[Andrew Lunn]

On Tue, May 25, 2004 at 10:40:09AM -0400, Eric Castle wrote:
> 
> Hello,
> 
> At the advice of Bob Koninckx, we're currently trying to get the latest
> anonymous CVS repository to work.  We seem to be doing something wrong when
> we run the configure script from it, though, in that when we run "make",
> none of the make files actually build anything.
> 
> Here's what we did:  
> 
> 1. Downloaded the CVS eCos stuff into a folder called cvs-ecos per the
> instructions on the webpage.
> 2. Set the path according to the instructions on the webpage for the eCos
> repository.
> 3. Made a "build" directory within cvs-ecos, switched into there.
> 4. Ran configure as follows:
> 	../ecos/configure --prefix=/usr/local/ecos --enable-debug
> 
> We tried some variants on this, with setting the prefix to ".", and not
> including it. We also tried including paths and version to tcl, but
> according to the README.host that comes with it, our install is exactly
> where is should be.
> 
> The trouble we have is when we run "make", nothing actually happens.

Do you get any errors or warnings when running configure?

By nothing, you really mean nothing, or does it actually do something?

I just tried configuring and building it now. It works are far as
trying to build the usb slave code and then fails. Thats probably
because i have a 2.6 kernel.

        Andrew

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

RE: [ECOS] Problem Installing CVS eCos

[Eric Castle]

Thanks, we eventually figured out what the difference was.  So, the
configure script and everything is for building the tools.  This is really
optional, considering there are pre-built ones that work fine in the 2.0
release.

And to just use more recent eCos files, we just switched the repository to
use the CVS files (either in our bash shell for ecosconfig, or in the
drop-down menu for the configtool).

-Eric

-----Original Message-----
From: Bob Koninckx [mailto:bob.koninckx@o-3s.com] 
Sent: Thursday, May 27, 2004 4:45 PM
To: Eric Castle
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problem Installing CVS eCos

On Tue, 2004-05-25 at 16:40, Eric Castle wrote:
> Hello,
> 
> At the advice of Bob Koninckx, we're currently trying to get the latest
> anonymous CVS repository to work.  We seem to be doing something wrong
when
> we run the configure script from it, though, in that when we run "make",
> none of the make files actually build anything.
> 
> Here's what we did:  
> 
> 1. Downloaded the CVS eCos stuff into a folder called cvs-ecos per the
> instructions on the webpage.

You checked it out, right?
something like

cvs -d :pserver:anonymous@sources.redhat.com:/cvs/ecos login
cvs -d :pserver:anonymous@sources.redhat.com:/cvs/ecos co ecos

[check the paths on the website...]


> 2. Set the path according to the instructions on the webpage for the eCos
> repository.
> 3. Made a "build" directory within cvs-ecos, switched into there.

Better make a build directory _outside_ the source tree. 

> 4. Ran configure as follows:
> 	../ecos/configure --prefix=/usr/local/ecos --enable-debug
> 

you do not need the configure script for building eCos, only for
building the tools. These are much easier downloaded from ecoscentric.
Instructions on how to do this are on the website.

> We tried some variants on this, with setting the prefix to ".", and not
> including it. We also tried including paths and version to tcl, but
> according to the README.host that comes with it, our install is exactly
> where is should be.
> 

construct your ecos makefiles using ecosconfig or configtool (which you
just downloaded from CVS).

> The trouble we have is when we run "make", nothing actually happens.
> 
> Can anyone suggest what we've missed?
> 

Basically, there is _no_ difference in _using_ eCos from CVS or from an
official release. The only difference lies in the fact that your using
much more up-to-date eCos source files.

> Thanks,
> 
> -Eric Castle
> 
> FEGI Project
> University of Michigan
> 
> 
> 
> 
> 




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

Re: [ECOS] Problem Installing CVS eCos

[Bob Koninckx]

On Tue, 2004-05-25 at 16:40, Eric Castle wrote:
> Hello,
> 
> At the advice of Bob Koninckx, we're currently trying to get the latest
> anonymous CVS repository to work.  We seem to be doing something wrong when
> we run the configure script from it, though, in that when we run "make",
> none of the make files actually build anything.
> 
> Here's what we did:  
> 
> 1. Downloaded the CVS eCos stuff into a folder called cvs-ecos per the
> instructions on the webpage.

You checked it out, right?
something like

cvs -d :pserver:anonymous@sources.redhat.com:/cvs/ecos login
cvs -d :pserver:anonymous@sources.redhat.com:/cvs/ecos co ecos

[check the paths on the website...]


> 2. Set the path according to the instructions on the webpage for the eCos
> repository.
> 3. Made a "build" directory within cvs-ecos, switched into there.

Better make a build directory _outside_ the source tree. 

> 4. Ran configure as follows:
> 	../ecos/configure --prefix=/usr/local/ecos --enable-debug
> 

you do not need the configure script for building eCos, only for
building the tools. These are much easier downloaded from ecoscentric.
Instructions on how to do this are on the website.

> We tried some variants on this, with setting the prefix to ".", and not
> including it. We also tried including paths and version to tcl, but
> according to the README.host that comes with it, our install is exactly
> where is should be.
> 

construct your ecos makefiles using ecosconfig or configtool (which you
just downloaded from CVS).

> The trouble we have is when we run "make", nothing actually happens.
> 
> Can anyone suggest what we've missed?
> 

Basically, there is _no_ difference in _using_ eCos from CVS or from an
official release. The only difference lies in the fact that your using
much more up-to-date eCos source files.

> Thanks,
> 
> -Eric Castle
> 
> FEGI Project
> University of Michigan
> 
> 
> 
> 
> 


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

[ECOS] Problem Installing CVS eCos

[Eric Castle]

Hello,

At the advice of Bob Koninckx, we're currently trying to get the latest
anonymous CVS repository to work.  We seem to be doing something wrong when
we run the configure script from it, though, in that when we run "make",
none of the make files actually build anything.

Here's what we did:  

1. Downloaded the CVS eCos stuff into a folder called cvs-ecos per the
instructions on the webpage.
2. Set the path according to the instructions on the webpage for the eCos
repository.
3. Made a "build" directory within cvs-ecos, switched into there.
4. Ran configure as follows:
	../ecos/configure --prefix=/usr/local/ecos --enable-debug

We tried some variants on this, with setting the prefix to ".", and not
including it. We also tried including paths and version to tcl, but
according to the README.host that comes with it, our install is exactly
where is should be.

The trouble we have is when we run "make", nothing actually happens.

Can anyone suggest what we've missed?

Thanks,

-Eric Castle

FEGI Project
University of Michigan






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