From: "Young Jay" <young_jay@sohu.com>
To: <sid@sources.redhat.com>
Subject: How to build SID for eCos application in cygwin environment?
Date: Thu, 22 May 2003 00:40:00 -0000 [thread overview]
Message-ID: <6000655.1053563998275.JavaMail.postfix@mx28.mail.sohu.com> (raw)
Hello, all:
I'm trying to buid SID for running eCos application on ARM7TDMI platform
in cygwin environment, with some problems happened. I proceeded following
the building instructions from http://www.asisi.co.uk/ecos_sid.html.
Because in that tutorial sid is built in Linux, there must be some difference
with cygwin environment. Thus I encountered building errors.
The output information when building sid is partly listed at the end.
Does anyone can give me some suggestions to solve the problem or provide
a building step in cygwin? Great thanks!
Best regards,
Young Jay
/**************************************************/
when execute:
$ ../src/configure --prefix=/opt/sid --exec-prefix=/opt/sid 2>&1 | tee configur
e.out
creating cache ./config.cache
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking build system type... i686-pc-cygwin
checking for i686-pc-cygwin-ar... no
checking for ar... ar
checking for i686-pc-cygwin-as... no
checking for as... as
checking for i686-pc-cygwin-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-cygwin-ld... /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../.
./i686-pc-cygwin/bin/ld.exe
checking for i686-pc-cygwin-nm... no
checking for nm... nm
checking for i686-pc-cygwin-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-cygwin-windres... no
checking for windres... windres
checking for i686-pc-cygwin-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-cygwin-objdump... no
checking for objdump... objdump
checking for i686-pc-cygwin-ar... no
checking for ar... ar
checking for i686-pc-cygwin-as... no
checking for as... as
checking for i686-pc-cygwin-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-cygwin-ld... no
checking for ld... ld
checking for i686-pc-cygwin-nm... no
checking for nm... nm
checking for i686-pc-cygwin-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-cygwin-windres... no
checking for windres... windres
checking whether to enable maintainer-specific portions of Makefiles... no
updating cache ./config.cache
creating ./config.status
creating Makefile
/**************************************************/
when executed "$ make all install":
at the end:
configuring in testsuite
running /bin/sh ../../../src/expect/testsuite/configure --build=i686-pc-cygwin
--host=i686-pc-cygwin --target=i686-pc-cygwin --prefix=/opt/sid --exec-prefix=/o
pt/sid --cache-file=../.././config.cache --srcdir=../../../src/expect/testsuite
loading cache ../.././config.cache
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
make: *** [configure-expect] Error 1
/******************************************************/
next reply other threads:[~2003-05-22 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 0:40 Young Jay [this message]
2003-05-22 19:36 ` Frank Ch. Eigler
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=6000655.1053563998275.JavaMail.postfix@mx28.mail.sohu.com \
--to=young_jay@sohu.com \
--cc=sid@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).