From: "Frank Ch. Eigler" <fche@redhat.com>
To: Young Jay <young_jay@sohu.com>
Cc: sid@sources.redhat.com
Subject: Re: How to build SID for eCos application in cygwin environment?
Date: Thu, 22 May 2003 19:36:00 -0000 [thread overview]
Message-ID: <20030522193546.GE7258@redhat.com> (raw)
In-Reply-To: <6000655.1053563998275.JavaMail.postfix@mx28.mail.sohu.com>
Hi -
> I'm trying to buid SID for running eCos application on ARM7TDMI platform
> in cygwin environment, with some problems happened. [...]
> [...]
> checking for Tcl configuration... configure: warning: Can't find Tcl configurati
> on definitions
> .: Can't open #: No such file or directory
> configure: error: ../../../src/expect/testsuite/configure failed for testsuite
> [...]
This sounds like a straightforward problem to solve, given one is set
up with a cygwin box to start with.
The sid faq page regarding building on cygwin is getting quite old.
It is definitely possible nowadays.
- FChE
next prev parent reply other threads:[~2003-05-22 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 0:40 Young Jay
2003-05-22 19:36 ` Frank Ch. Eigler [this message]
2003-05-23 7:14 Young Jay
2003-05-23 8:52 ` Ben Elliston
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=20030522193546.GE7258@redhat.com \
--to=fche@redhat.com \
--cc=sid@sources.redhat.com \
--cc=young_jay@sohu.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).