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: Re: mingw32 target broken [cygwin as well] [the saga continues]
Date: Sat, 08 Dec 2001 16:04:00 -0000	[thread overview]
Message-ID: <86itbhz2gt.fsf@megacz.com> (raw)
In-Reply-To: Jeff Sturm's message of "Sat, 8 Dec 2001 17:14:32 -0500 (EST)"


Jeff Sturm <jsturm@one-point.com> writes:
> Note however that gcc needs to find the target headers in
> $prefix/<target>/include, so you'll want to copy these before
> configuring gcc

Ah, this was the problem. I also had to compile a set of
cross-binutils. This time I got much farther -- it seems to get most
of the C compiler to compile, but I'm running into problems with
libstdc++... has anybody seen anything like this before?

../src/configure \
                 --prefix=/usr \
                 --enable-shared \
                 --enable-languages=c,c++,java \
                 --disable-nls \
                 --with-as=/usr/cross-binutils/i686-pc-mingw32/bin/as \
                 --target=i686-pc-mingw32 \
                 --with-gnu-ld \
                 --with-gnu-as \
                 --with-ld=/usr/cross-binutils/i686-pc-mingw32/bin/ld

/home/megacz/gcc-3.1/bin/gcc/xgcc -B/home/megacz/gcc-3.1/bin/gcc/ -nostdinc++ -L/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/src -L/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/src/.libs -B/usr/i686-pc-mingw32/bin/ -B/usr/i686-pc-mingw32/lib/ -isystem /usr/i686-pc-mingw32/include -nostdinc++ -I/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32 -I/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include -I../../../../src/libstdc++-v3/libsupc++ -I../../../../src/libstdc++-v3/libmath -g -O2 -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c basic_file.cc -o basic_file.o
In file included from /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/bits/locale_facets.h:54,
                 from /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/bits/basic_ios.h:41,
                 from /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/bits/std_ios.h:51,
                 from /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/bits/basic_file.h:45,
                 from basic_file.cc:34:
/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:46: `
   _U' was not declared in this scope
/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:47: `
   _L' was not declared in this scope
/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:48: `
   _U' was not declared in this scope
/home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:48: `
   _L' was not declared in this scope

  reply	other threads:[~2001-12-09  0:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 21:06 mingw32 target broken Adam Megacz
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         ` Adam Megacz [this message]
2001-12-08 18:19           ` mingw32 target broken [cygwin as well] [the saga continues] 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

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=86itbhz2gt.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).