public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: How to build ecosconfig?
Date: Tue, 22 May 2007 20:58:00 -0000	[thread overview]
Message-ID: <f2vk3t$4sf$1@sea.gmane.org> (raw)
In-Reply-To: <20070522202509.GA2989@lunn.ch>

On 2007-05-22, Andrew Lunn <andrew@lunn.ch> wrote:

>> Can somebody point me to instructions for building ecosconfig?
>> Following the instructions in README.host gets me this:
>> 
>> $ ls -l ~/ecos/host
>> total 100
>> drwxr-xr-x 2 grante users  4096 May 22 14:52 CVS/
>> -rw-r--r-- 1 grante users  4442 Feb 12  2003 ChangeLog
>> -rw-r--r-- 1 grante users  1721 Aug 11  2002 Makefile.am
>> -rw-r--r-- 1 grante users 10740 Feb 12  2003 Makefile.in
>> -rw-r--r-- 1 grante users  1805 Aug 11  2002 acinclude.m4
>> -rw-r--r-- 1 grante users  6180 Aug 11  2002 aclocal.m4
>> -rwxr-xr-x 1 grante users 41952 Aug 11  2002 configure*
>> -rw-r--r-- 1 grante users  2728 Aug 11  2002 configure.in
>> drwxr-xr-x 4 grante users  4096 May 22 14:52 infra/
>> drwxr-xr-x 5 grante users  4096 May 22 14:52 libcdl/
>> drwxr-xr-x 8 grante users  4096 May 22 14:52 tools/
>> 
>> $ ~/ecos/host/configure
>> configure: error: can not find sources in /home/grante/ecos/host or ..
>
> I use the top level configure script, not the one in host.

After examining the host/configure script, I figured out that
to build the host tools you also have to download the acsupport
directory and place it so that it's a sibling to the host
directory.  That ought be documented in the README.host file.

Using the newly built ecosconfig appears to solve the problem
where v2_0 of the net template was being used instead of the
current version.

I've still not been able to figure out why the older version of
ecosconfig decides to use v2_0 of the net template when I build
from one source tree and decides on current if I build from a
different source tree.

The only difference between the trees is that some of the files
in one tree have DOS line endings.  I ran ecos.db and all of
the .ect files through dos2unix, and that didn't seem to help.

-- 
Grant Edwards                   grante             Yow! I demand IMPUNITY!
                                  at               
                               visi.com            


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

  reply	other threads:[~2007-05-22 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 20:25 [ECOS] " Grant Edwards
2007-05-22 20:35 ` Andrew Lunn
2007-05-22 20:58   ` Grant Edwards [this message]
2007-05-22 21:59 ` Bart Veer

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='f2vk3t$4sf$1@sea.gmane.org' \
    --to=grante@visi.com \
    --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).