public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adam Megacz <gcc@lists.megacz.com>
To: gcc@gcc.gnu.org
Subject: mingw32 target broken
Date: Fri, 07 Dec 2001 21:06:00 -0000	[thread overview]
Message-ID: <86g06mi9rn.fsf@megacz.com> (raw)


Hrm, I checked this out a few mintues ago... does anybody know what
the problem might be? I'm building on an i686-gnu-linux host...

/home/megacz/gcc-3.1/bin/gcc/xgcc -B/home/megacz/gcc-3.1/bin/gcc/ -B/usr/mingw32/bin/ -B/usr/mingw32/lib/ -isystem /usr/mingw32/include -O2 -I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -I../../src/gcc/../winsup/w32api/include -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -I../../src/gcc/../include -DL_chkstk -xassembler-with-cpp -c ../../src/gcc/config/i386/cygwin.asm -o libgcc/./_chkstk.o
/home/megacz/gcc-3.1/bin/gcc/xgcc -B/home/megacz/gcc-3.1/bin/gcc/ -B/usr/mingw32/bin/ -B/usr/mingw32/lib/ -isystem /usr/mingw32/include -O2 -I../../src/gcc/../winsup/include -I../../src/gcc/../winsup/cygwin/include -I../../src/gcc/../winsup/w32api/include -DCROSS_COMPILE -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include   -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config -I../../src/gcc/../include  -DL_muldi3 -c ../../src/gcc/libgcc2.c -o libgcc/./_muldi3.o
In file included from ../../src/gcc/config/i386/mingw32.h:25,
                 from tconfig.h:4,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:31:19: stdio.h: No such file or directory
In file included from ../../src/gcc/config/i386/mingw32.h:25,
                 from tconfig.h:4,
                 from ../../src/gcc/libgcc2.c:36:
../../src/gcc/config/i386/cygwin.h:435: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:435: warning: function declaration isn't a prototype
../../src/gcc/config/i386/cygwin.h:437: parse error before '*' token
../../src/gcc/config/i386/cygwin.h:437: warning: function declaration isn't a prototype
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/megacz/gcc-3.1/bin/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/megacz/gcc-3.1/bin/gcc'
make: *** [all-gcc] Error 2

             reply	other threads:[~2001-12-08  5:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 21:06 Adam Megacz [this message]
2001-12-07 22:01 ` Adam Megacz
     [not found]   ` <20011208003722.A14955@mediaone.net>
2001-12-07 23:12     ` mingw32 target broken [cygwin as well] Adam Megacz
2001-12-07 23:40       ` Craig Rodrigues
2001-12-08  0:00         ` mingw32 target broken [cygwin as well] [didn't know cross-compilers were such an ordeal] Adam Megacz
2001-12-08 16:00           ` Jeff Sturm
2001-12-08 16:05             ` Adam Megacz
2001-12-08 14:42       ` mingw32 target broken [cygwin as well] Jeff Sturm
2001-12-08 16:04         ` mingw32 target broken [cygwin as well] [the saga continues] Adam Megacz
2001-12-08 18:19           ` Craig Rodrigues
2001-12-08 18:30             ` Adam Megacz
2001-12-08 18:39               ` Craig Rodrigues
2001-12-08 18:56                 ` Adam Megacz
2001-12-09  9:07               ` Jeff Sturm
2001-12-09 20:38                 ` Adam Megacz
2001-12-10 12:36                 ` DJ Delorie
2001-12-10 12:48                   ` Joseph S. Myers
2001-12-10 12:57                     ` DJ Delorie
2001-12-10 21:06                   ` Jeff Sturm
2001-12-10 21:08                     ` DJ Delorie
2001-12-08  8:43 mingw32 target broken Danny Smith
2001-12-08 16:24 ` Adam Megacz

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=86g06mi9rn.fsf@megacz.com \
    --to=gcc@lists.megacz.com \
    --cc=gcc@gcc.gnu.org \
    /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).