From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32315 invoked by alias); 28 May 2004 16:46:46 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 32307 invoked from network); 28 May 2004 16:46:46 -0000 Received: from unknown (HELO sccrmhc11.comcast.net) (204.127.202.55) by sourceware.org with SMTP; 28 May 2004 16:46:46 -0000 Received: from mark2 (bgp996206bgs.nanarb01.mi.comcast.net[68.40.48.206]) by comcast.net (sccrmhc11) with SMTP id <20040528164653011009g4aee>; Fri, 28 May 2004 16:46:53 +0000 From: "Eric Castle" To: Cc: Date: Sat, 29 May 2004 21:11:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <1085694297.2567.9.camel@pc-002.vuilenbos.net> Subject: RE: [ECOS] Problem Installing CVS eCos X-SW-Source: 2004-05/txt/msg00392.txt.bz2 Message-ID: <20040529211100.awcbauDKP-luheqpwN7-e0POiP7oJGRf8uMFDEw4VE8@z> 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