From: Bob Koninckx <bob.koninckx@o-3s.com>
To: Eric Castle <ecastle@umich.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problem Installing CVS eCos
Date: Thu, 27 May 2004 22:15:00 -0000 [thread overview]
Message-ID: <1085694297.2567.9.camel@pc-002.vuilenbos.net> (raw)
In-Reply-To: <200405251452.i4PEqrUV014326@imr5.netsolmail.com>
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
next parent reply other threads:[~2004-05-27 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405251452.i4PEqrUV014326@imr5.netsolmail.com>
2004-05-27 22:15 ` Bob Koninckx [this message]
2004-05-29 21:11 ` Eric Castle
[not found] <E1BSdIM-0001kr-00@londo.lunn.ch>
2004-05-25 19:28 ` Andrew Lunn
2004-05-25 16:11 Eric Castle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1085694297.2567.9.camel@pc-002.vuilenbos.net \
--to=bob.koninckx@o-3s.com \
--cc=ecastle@umich.edu \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).