From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Bob Brusa <bob.brusa@gmail.com>
Cc: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] No host branch in my checkedout ecos tree
Date: Thu, 16 Jan 2014 17:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1401162003320.4527@foo.bar.baz> (raw)
In-Reply-To: <52D80F2F.90903@gmail.com>
On Thu, 16 Jan 2014, Bob Brusa wrote:
> Am 16.01.2014 16:19, schrieb Sergei Gavrikov:
> > On Thu, 16 Jan 2014, Bob Brusa wrote:
> >
> >
> > And below does not work in Cygwin?
> >
> > cd /opt
> > cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P ecos
> > cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P host
> >
> Sure, both worked. I also understand now, that ecos and host are modulenames.
> May be I was misled by the layout (see also attachment) as shown on the web
> interface of ecos-cvs. There it looks as if host is simply part of the ecos
> tree. See http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/?cvsroot=ecos
URL was sufficient, no PNG, please :-)
> > Check that you have set ECOS_REPOSITORY variable.
> >
> > echo $ECOS_REPOSITORY ;# What have you seen?
> >
> This seems ok. I get:
> rwb@w500 /opt
> $ echo $ECOS_REPOSITORY
> /cygdrive/c/cygwin/opt/ecos
Nope! It must be <cygwin_abs_path_name>/ecos/packages
^^^^^^^^
> > > $ c:/cygwin/opt/ecos/host/configure --with-tcl=c:/cygwin/lib/tcl8.5
> > > --with-tk=c:/cygwin/lib/tk8.5
> > [snip]
> > > c:/cygwin/opt/ecos/host/configure: line 2990: test: too many arguments
> >
> > Install Tcl/Tk *8.4* dev. packages.
>
> Ok, I am going to test it also with tcl8.4/tk8.4 instead of tcl8.5/tk8.5
AFAIR, eCos configure checks Tcl/Tk version and expects Tcl/Tk 8.4.
> > Hope that you read README.host at least from here
> >
> > It is necessary to use a separate build tree rather than build
> > directly in the source tree. This is enforced by the configure scripts.
> >
> > $ mkdir build
> > $ cd build
> >
>
> That's what I did - except that my new directory is named host and is
> in opt (I follow method 2 outlined in README.host). I then started
> the configure from within opt/host and got all these errors at line
> 2990. I knew it would not be easy, but hell, I need a working
Use some kind of paste-bin and paste config.log there.
> executable of configtool. The one of 24-Apr-2012 does not work on my
> Windows 7 /cygwin PC.
I afraid that you won't get GUI (configtool), first thing to get is CLI
(ecosconfig). IMO, more bloodless way to get working configtool is to
install Linux on Virtual Machine (virtualbox/vmware).
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2014-01-16 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 16:38 Bob Brusa
2014-01-15 19:35 ` Sergei Gavrikov
2014-01-16 15:48 ` Bob Brusa
2014-01-16 16:20 ` Sergei Gavrikov
2014-01-16 17:03 ` Bob Brusa
[not found] ` <52D80F2F.90903@gmail.com>
2014-01-16 17:19 ` Sergei Gavrikov [this message]
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=alpine.DEB.2.00.1401162003320.4527@foo.bar.baz \
--to=sergei.gavrikov@gmail.com \
--cc=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).