From: "Huang Qiang" <jameshq@liverpool.ac.uk>
To: "eCos" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Problem with building the ARM-development tools?
Date: Mon, 14 May 2001 09:24:00 -0000 [thread overview]
Message-ID: <KIEBICHBADHFCLGCKOPDGELNCBAA.jameshq@liv.ac.uk> (raw)
Dear All:
I encounter a lot of problems when I building the development tools for
ARM board.
Here are the steps I followed exactly.( Please point out the mistake for me
. Thanks a lot! )
( I am on Windows2000 platform, and I have download the cygwin1.3.1. On my
computer I have c:(Harddisk) d:(HardDisk) e:(as CD-RoM).
Cygwin is installed in: c:/cygwin )
1. $ uname -r
1.3.1(0.38/3/2)
2. $ mount -f c:/ /c
$ mount -f d:/ /d
$ mount -f e:/ /e
3. "download the files": (1) binutils-2.10.1.tar.bz2
(2) gcc-core-2.95.2.tar.bz2
(3) gcc-g++-2.95.2.tar.bz2
(4) insight-5.0.tar.bz2
(5) ecos-gcc-2952.pat (patch file)
(6) insight-tcl.pat (patch file)
and store in c:/cygwin directory.
4. $ mkdir -p /src/binutils /src/gcc /src/gdb
5. $ cd /src/binutils
$ bunzip2 < /binutils-2.10.1.tar.bz2 | tar xvf -
$ cd /src/gcc
$ bunzip2 < /gcc-core-2.95.2.tar.bz2 | tar xvf -
$ bunzip2 < /gcc-g++-2.95.2.tar.bz2 | tar xvf -
$ cd /src/gdb
$ bunzip2 < /insight-5.0.tar.bz2 | tar xvf -
6. $ echo $TEMP
/c/winnt/temp
7. "use mount to examine my system":
$ mount
c:\cygwin\bin on /usr/bin type system (textmode)
c:\cygwin\lib on /usr/lib type system (textmode)
c:\cygwin\tmp on /tmp type user (binmode)
c:\winnt\temp on /c/winnt/temp type user (binmode)
c:\cygwin on / type system (textmode)
c: on /c type user (textmode)
d: on /d type user (textmode)
e: on /e type user (textmode)
8. $ cd /src/gdb/insight-5.0
$ tr -d '\r' < /insight-tcl.pat | patch -p0
9. $ cd /src/gcc/gcc-2.95.2
$ tr -d '\r' < ecos-gcc-2952.pat | patch -p0
10. $ contrib/egcs_update --touch
11. $ export MAKE_MODE=UNIX
12. $ mkdir -p /tmp/build/binutils
$ cd /tmp/build/binutils
$ /src/binutils/binutils-2.10.1/configure --target=arm-elf \
--prefix=/tools \
--exec-prefix=/tools/H-i686-pc-cygwin \
-v 2>&1 | tee configure.out
13. $ make -w all install 2>&1 | tee make.out
14. $ PATH=/tools/H-i686-pc-cygwin/bin:$PATH ; export PATH
$ mkdir -p /tmp/build/gcc
$ cd /tmp/build/gcc
$ /src/gcc/gcc-2.95.2/configure --target=arm-elf \
--prefix=/tools \
--exec-prefix=/tools/H-i686-pc-cygwin \
--with-gnu-as --with-gnu-ld --with-newlib \
-v 2>&1 | tee configure.out
15. $ make -w all-gcc install-gcc \
LANGUAGES="c c++" 2>&1 | tee make.out
16. $ mkdir -p /tmp/build/gdb
$ cd /tmp/build/gdb
$ /src/gdb/insight-5.0/configure --target=arm-elf \
--prefix=/tools \
--exec-prefix=/tools/H-i686-pc-cygwin \
-v 2>&1 | tee configure.out
17. $ make -w all install 2>&1 | tee make.out
" Now encounter problems here, it seems it can solve something with the
win32api .h files". problems shows:
/usr/include/w32api/winnt.h:48: parse error before `CCHAR'
and many the same type errors following this one.
and the in winnt.h line 48 shows:
typedef CHAR CCHAR;
Can anybody help me. Thank you very much !!!
Best regards!
james
next reply other threads:[~2001-05-14 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 9:24 Huang Qiang [this message]
2001-05-14 10:32 ` Jonathan Larmour
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=KIEBICHBADHFCLGCKOPDGELNCBAA.jameshq@liv.ac.uk \
--to=jameshq@liverpool.ac.uk \
--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).