From: Andreas.Karlsson@combitechsystems.com
To: crossgcc@sourceware.cygnus.com
Subject: error while making gcc
Date: Thu, 29 Jun 2000 00:59:00 -0000 [thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B01F97E57@pluto.combitech.se> (raw)
Hi,
I'm running NT 4.0 and the latest version of cygwin.
Following the installation instructions on
http://sourceware.cygnus.com/ecos/tools/win-arm-elf.html everything works
fine until making GCC.
Is there anybody who has a clue why the error occurs?
I have not done anything in cygwin since I installed it, just been following
the eCos installation pages. Is there maybe something I have to set or
define in cygwin?
Some days ago I had a problem with arm.h (probably DOS enters) but this was
solved when I received a new file, is there a connection?
/Andreas
make: Entering directory `/tmp/build/gcc'
make[1]: Entering directory `/tmp/build/gcc/libiberty'
make[2]: Entering directory `/tmp/build/gcc/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/build/gcc/libiberty/testsuite'
make[1]: Leaving directory `/tmp/build/gcc/libiberty'
make[1]: Entering directory `/tmp/build/gcc/texinfo'
make all-recursive
make[2]: Entering directory `/tmp/build/gcc/texinfo'
Making all in intl
make[3]: Entering directory `/tmp/build/gcc/texinfo/intl'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/build/gcc/texinfo/intl'
Making all in lib
make[3]: Entering directory `/tmp/build/gcc/texinfo/lib'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/build/gcc/texinfo/lib'
Making all in makeinfo
make[3]: Entering directory `/tmp/build/gcc/texinfo/makeinfo'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/tmp/build/gcc/texinfo/makeinfo'
make[2]: Leaving directory `/tmp/build/gcc/texinfo'
make[1]: Leaving directory `/tmp/build/gcc/texinfo'
make[1]: Entering directory `/tmp/build/gcc/gcc'
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 \
-DPREFIX=\"/tools\" \
-c `echo /src/gcc/gcc-2.95.2/gcc/prefix.c | sed 's,^\./,,'`
In file included from
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/windef.h:141,
from
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/windows.h:96,
from /src/gcc/gcc-2.95.2/gcc/prefix.c:69:
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/winnt.h:2062: two
or more data types in declaration of `type name'
make[1]: *** [prefix.o] Error 1
make[1]: Leaving directory `/tmp/build/gcc/gcc'
make: *** [all-gcc] Error 2
make: Leaving directory `/tmp/build/gcc'
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-29 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 0:59 Andreas.Karlsson [this message]
2000-06-29 17:06 ` Jonathan Larmour
2000-07-13 10:10 Dan Carlson
2000-07-13 10:26 ` Jonathan Larmour
2000-07-14 5:13 Clive Davies
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=2253171AF143D21185A60000F8FA748B01F97E57@pluto.combitech.se \
--to=andreas.karlsson@combitechsystems.com \
--cc=crossgcc@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).