From: "Stephan T. Lavavej" <stl@caltech.edu>
To: "GCC" <gcc@gcc.gnu.org>
Subject: Re: Failure crossing gcc 3.3.3 from GNU/Linux to MinGW
Date: Sat, 20 Mar 2004 13:59:00 -0000 [thread overview]
Message-ID: <20040320050016.5A7E8109A66@earth-ox.its.caltech.edu> (raw)
I got the cross gcc to compile by using this patch:
diff -aur gcc-3.3.3-truemingw/libstdc++-v3/include/bits/char_traits.h
gcc-3.3.3-truemingw-new/libstdc++-v3/include/bits/char_traits.h
--- gcc-3.3.3-truemingw/libstdc++-v3/include/bits/char_traits.h 2003-10-07
18:15:05.000000000 -0700
+++ gcc-3.3.3-truemingw-new/libstdc++-v3/include/bits/char_traits.h
2004-03-19 20:26:29.000000000 -0800
@@ -181,7 +181,7 @@
};
-#if defined (_GLIBCPP_USE_WCHAR_T) || defined (_GLIBCPP_USE_WSTRING)
+#if 0
/// 21.1.3.2 char_traits specializations
template<>
struct char_traits<wchar_t>
However, compiling the crossed-native gcc fails with:
make[1]: Entering directory `/home/stl/cross/wingcc-build/gcc'
TM_DEFINES="" \
HEADERS="auto-host.h ansidecl.h i386/xm-mingw32.h i386/cygming.h
i386/mingw32.h defaults.h" XM_DEFINES="POSIX" \
TARGET_CPU_DEFAULT="TARGET_CPU_DEFAULT_pentiumpro" \
/bin/sh /home/stl/cross/wingcc-src/gcc/mkconfig.sh config.h
TM_DEFINES="" \
HEADERS="auto-build.h ansidecl.h i386/cygming.h i386/mingw32.h defaults.h"
XM_DEFINES="POSIX" \
TARGET_CPU_DEFAULT="TARGET_CPU_DEFAULT_pentiumpro" \
/bin/sh /home/stl/cross/wingcc-src/gcc/mkconfig.sh hconfig.h
make[1]: *** No rule to make target `auto-build.h', needed by `gengenrtl.o'.
Stop.
make[1]: Leaving directory `/home/stl/cross/wingcc-build/gcc'
make: *** [all-gcc] Error 2
Any ideas?
Stephan T. Lavavej
next reply other threads:[~2004-03-20 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 13:59 Stephan T. Lavavej [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 5:00 Stephan T. Lavavej
2004-03-20 4:53 Stephan T. Lavavej
2004-03-20 5:00 ` llewelly
2004-03-20 3:46 Stephan T. Lavavej
2004-03-20 4:50 ` Gabriel Dos Reis
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=20040320050016.5A7E8109A66@earth-ox.its.caltech.edu \
--to=stl@caltech.edu \
--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).