public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jens.ohlund@secrc.abb.se
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Problems making gcc
Date: Fri, 09 Jun 2000 02:18:00 -0000	[thread overview]
Message-ID: <OFC5B1690C.5916E849-ONC12568F9.00320CEE@secrc.abb.se> (raw)

My problem is that even if i follow the given instructoins it crashes...

I run NT4 and i want to install ecos 1.3.1 with insight for the ARM. (AEB-1).

When following the instructions on the homepage I first installed cygwin, no problems.
Then installed ecos, no problem.
Mounted c: and d:, no rpoblem.
Unpacking everything, no problem.
Patching gcc and insight with given methof (tr -d ...), no problem
Configuring and building binutils, no problem
Configuring gcc, ok i think.
Building gcc, crash.

This is what happened when it starts crashing:
gcc -DCROSS_COMPILE -DIN_GCC     -g -O2  -DHAVE_CONFIG_H    -I. -I/src/gcc/gcc-2.95.2/gcc -I/src/gcc/gcc-2.95.2/gcc/config -I/src/gcc/gcc-2.95.2/gcc/../include \
  -DGCC_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/include\" \
  -DGPLUSPLUS_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../..`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/[^/]*|/..|g'`/include/g++-3\" \
  -DLOCAL_INCLUDE_DIR=\"/tools/include\" \
  -DCROSS_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/$||' -e 's|^[^/]|/|' -e 's|/[^/]*|../|g'`arm-elf/sys-include\" \
  -DTOOL_INCLUDE_DIR=\"/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/../../../`echo /tools/H-i686-pc-cygwin | sed -e 's|^/tools||' -e 's|/$||' -e 's|^[^/]|/|' -e 's|/[^/]*|../|g'`arm-elf/include\" \
  -c `echo /src/gcc/gcc-2.95.2/gcc/cccp.c | sed 's,^\./,,'`
In file included from /src/gcc/gcc-2.95.2/gcc/config/arm/aout.h:301,
                 from /src/gcc/gcc-2.95.2/gcc/config/arm/elf.h:354,
                 from /src/gcc/gcc-2.95.2/gcc/config/arm/unknown-elf.h:171,
                 from tm.h:6,
                 from /src/gcc/gcc-2.95.2/gcc/config/i386/xm-i386.h:43,
                 from config.h:8,
                 from /src/gcc/gcc-2.95.2/gcc/cccp.c:21:
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: parse error before `{'
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: warning: unknown escape sequence: `\' followed by char code 0xd
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:227: warning: unknown escape sequence: `\' followed by char code 0xd
/src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:228: warning: unknown escape sequence: `\' followed by char code 0xd

And it continues like that ALOT.

I have used binutils-20000608, gcc 2.95.2. Installed cygwin 1.1.2. And tried lots more. Searched for it in the archives. Seen some
ideas but none worked. Now i've tried to install this for 3 days and I'm desperate. ANYbody got an idea ?

Yours, soon-to-be-hairless
Jens Ohlund

             reply	other threads:[~2000-06-09  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09  2:18 jens.ohlund [this message]
2000-06-09  4:15 ` Hugo 'NOx' Tyson
2000-06-09  4:26   ` Alex Schuilenburg
2000-06-09  7:37     ` Jonathan Larmour
2001-09-05  0:10   ` Hugo 'NOx' Tyson

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=OFC5B1690C.5916E849-ONC12568F9.00320CEE@secrc.abb.se \
    --to=jens.ohlund@secrc.abb.se \
    --cc=ecos-discuss@sourceware.cygnus.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).