From: "Stephane Aubert" <stephane.aubert@coronis-systems.com>
To: "Darren Addicott" <DarrenA@akhter.co.uk>,
<binutils@sources.redhat.com>, <ecos-cvs@sources.redhat.com>,
<crossgcc@sources.redhat.com>, <gcc@gcc.gnu.org>,
"'GNUTeam'" <gnuteam@kpit.com>, <insight@sources.redhat.com>,
<irox@redhat.com>
Subject: Windows Error when I want to start arm-elf-gdb
Date: Mon, 03 Dec 2001 08:56:00 -0000 [thread overview]
Message-ID: <003d01c17c1b$424d2dc0$0167010a@coronis> (raw)
Message-ID: <20011203085600.bcA8aTg5W2fuZ61Cwhn-IkDziwkP85zjFh_MKzfu9kY@z> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
I'm working on
W98 and I'm trying to install the ARM development tools for Ecos (with
Cygwin). Â Im following the instruction on the internet page "Building
the ARM development tools for
Wondows" (sources.redhat.com/ecos/tools/win-arm-elf.html). Â So, I
configure the GNU Binary Utilities (binutils-2.10.1.tar.bz2) with
the following cmds: Â Â Â 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  -> OK And I Build and install the GNU
Binary Utilities: make -w all install 2>&1 | tee
make.out -> OK Then I configure GCC
(gcc-core-2.95.2.tar.bz2 & gcc-g++-2.95.2.tar.bz2): Â
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 -> OK And I Build and install GCC: make -w
all-gcc install-gcc \ LANGUAGES="c c++" 2>&1 | tee
make.out -> OK
Â
Then I configure the Insight
GDBÂ (insight-5.0.tar.bz2): Â Â Â mkdir -p
/tmp/build/gdb    cd /tmp/build/gdb   Â
/src/gcc/insight-5.0/configure --target=arm-elf
\ Â Â Â Â Â --prefix=/tools
\ Â Â Â Â Â --exec-prefix=/tools/H-i686-pc-cygwin
\ Â Â Â Â Â Â -v 2>&1 | tee
configure.out -> OK And I Build and install GDB: make -w
all install CC='gcc -mwin32' 2>&1 | tee make.out
Â
-> OK
Â
Â
But when I want to use the Insight GDB, I have a big Windows
Error (see attach : error arm-elf-gdb.gif).
Â
-> NOK !!!!
Â
I don't know what I must to do.
I have already check the version of the tcl (version 8.0). This is the good
version.
So if somebody can help me!!! I will apreciate.
Â
Stephane.Â
Â
Attachment:
error arm-elf-gdb.gif
Description: GIF image
next reply other threads:[~2001-12-03 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 18:42 Stephane Aubert [this message]
2001-10-07 13:46 ` Alan Lehotsky
2001-10-07 14:33 ` Keith Seitz
2001-12-04 11:13 ` Keith Seitz
2001-12-04 4:55 ` Alan Lehotsky
2001-12-03 8:56 ` Stephane Aubert
2001-10-08 7:55 kyle Loudon
2001-10-09 8:02 ` Fernando Nasser
2001-12-05 6:51 ` Fernando Nasser
2001-10-09 8:15 ` Keith Seitz
2001-12-05 8:48 ` Keith Seitz
2001-12-04 16:01 ` kyle Loudon
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='003d01c17c1b$424d2dc0$0167010a@coronis' \
--to=stephane.aubert@coronis-systems.com \
--cc=DarrenA@akhter.co.uk \
--cc=binutils@sources.redhat.com \
--cc=crossgcc@sources.redhat.com \
--cc=ecos-cvs@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gnuteam@kpit.com \
--cc=insight@sources.redhat.com \
--cc=irox@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).