From: danc@iobjects.com (Dan Conti)
To: "ecos discuss2" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] problems with ecosconfig
Date: Tue, 27 Mar 2001 14:56:00 -0000 [thread overview]
Message-ID: <CAEMICOOKMKAGHPNGNFNAEHICHAA.danc@iobjects.com> (raw)
In-Reply-To: <3AC113A3.AD86F2BF@redhat.com>
thanks for the suggestion, i ran through my setup again to double check
everything and realized that i had copied my updated ecosconfig into the
current directory and didn't ./ it, forgetting that . isn't in the path.
hence it was still catching the old tool. that was indeed the problem.
greatly appreciated jonathan, thank you
-Dan
> -----Original Message-----
> From: jlarmour@cambridge.redhat.com
> [ mailto:jlarmour@cambridge.redhat.com]On Behalf Of Jonathan Larmour
> Sent: Tuesday, March 27, 2001 2:27 PM
> To: Dan Conti
> Cc: ecos discuss2
> Subject: Re: [ECOS] problems with ecosconfig
>
>
> Dan Conti wrote:
> >
> > at this moment, it's just one tree on my machine. the two
> different configs
> > both point to the same tree. my .ecc file is complete, from
> what i can see.
> > some more clues, a snippet from the ecc:
>
> One thought that just occurred to me - are you definitely using the same
> ecosconfig on both machines, i.e. the most recent one. I think
> what you see
> happening could occur if one of them was old. And are you sure no error
> messages are produced by ecosconfig itself when it does an "ecosconfig
> tree" with that configuration?
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
>
next prev parent reply other threads:[~2001-03-27 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 12:02 Dan Conti
2001-03-27 13:27 ` Jonathan Larmour
2001-03-27 14:03 ` Dan Conti
2001-03-27 14:26 ` Jonathan Larmour
2001-03-27 14:56 ` Dan Conti [this message]
2001-03-28 2:00 ` Hugo 'NOx' Tyson
2006-05-31 18:02 [ECOS] Problems " Денис Шевченко
2006-05-31 18:37 ` Andrew Lunn
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=CAEMICOOKMKAGHPNGNFNAEHICHAA.danc@iobjects.com \
--to=danc@iobjects.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).