public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Raj Menon <rxmtemp@mcdata.com>
To: gnu-win32@cygnus.com
Subject: i960 cross compiling...
Date: Mon, 19 Jan 1998 10:32:00 -0000	[thread overview]
Message-ID: <s4c339b4.072@mcdata.com> (raw)

HELP!

I am using the GNUWIN32 distribution and trying to build a
cross-compiler for the i960 (i960-coff from i386-pc-cygwin32).
It seems like binutils, GAS, LD etc build fine.  GCC on the other
hand, does not.   I get the following error:

> touch stmp-multilib
> /apps/gnuwin32/b18/cdk/gcc/xgcc -B/apps/gnuwin32/b18/cdk/gcc/
-DCROSS_COMPILE -DIN_GCC -O2 -I./include -c ./libgcc1-test.c
> Testing libgcc1.  Ignore linker warning messages.
> /apps/gnuwin32/b18/cdk/gcc/xgcc -B/apps/gnuwin32/b18/cdk/gcc/
-DCROSS_COMPILE -DIN_GCC -O2 -I./include libgcc1-test.o -o
libgcc1-test -nostartfiles -nostdlib '/apps/gnuwin32/b18/cdk/gcc/xgcc
-B/apps/gnuwin32/b18/cdk/gcc/ --print-libgcc-file-name'
> libgcc1-test.o: file not recognized: File format not recognized
> xgcc: Internal compiler error: program ld got fatal signal 1
> make: *** [libgcc1-test] Error 1
> make: *** [all-gcc] Error 2

I have been trying to build a cross compiler for about a week now.
I have tried building Intel's CTOOLS 5.1 (ar does not build correctly
and thus none of the lib's can be built).  I tried the gcc-2.7.3 distribution,
which also dies.  I tried the egcs-1.0.1 distribution, which also
dies.  If anyone can help, I would greatly appreciate it.  I need the
compiler ASAP.

Thanks.

-raj

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

                 reply	other threads:[~1998-01-19 10:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=s4c339b4.072@mcdata.com \
    --to=rxmtemp@mcdata.com \
    --cc=gnu-win32@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).