public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Steve Wheeler <swheeler@vestatech.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] configtool help needed
Date: Tue, 02 Aug 2005 19:42:00 -0000	[thread overview]
Message-ID: <6.0.0.22.0.20050802130148.03fb8880@192.168.0.19> (raw)

I'm working on a platform HAL for an LPC2292-based board, and I'm running 
into a problem with configtool on a Windows XP/Cygwin platform. When I 
select BUILD, I get a series of errors reporting that various procedures 
are "defined both normally and as an alias."

I searched for that error message in the message archives, and found the 
advice to upgrade my tools. I did that and changed the build tool path in 
configtool to point to the new tools, but it had no effect. However, I 
discovered that setting the appropriate search path in a Cygwin command 
window and executing make from the command line produced a build without 
errors.

This tells me that configtool isn't using the build tool path I give it. I 
was presuming that it was, because it would tell me if I pointed it to a 
directory that didn't have the tools in it. Is there something unobvious I 
need to know to make it work, or do I just have to ignore configtool and 
work from the command line?

Also, when I select "Configuration Tool Help" from the Help menu, it tells 
me "c is not a registered protocol." I've installed from scratch twice 
already - how do I get access to the online help?

-- 
Steve Wheeler
Vesta Technology, Inc.



This e-mail was scanned for viruses using BitDefender
Sent by 602Pro LAN SUITE - http://www.software602.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:[~2005-08-02 19:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6.0.0.22.0.20050802130148.03fb8880@192.168.0.19 \
    --to=swheeler@vestatech.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).