From: llewelly@xmission.com
To: <stl@caltech.edu>
Cc: "GCC" <gcc@gcc.gnu.org>
Subject: Re: Failure crossing gcc 3.3.3 from GNU/Linux to MinGW
Date: Sat, 20 Mar 2004 05:00:00 -0000 [thread overview]
Message-ID: <s3r65d0b50f.fsf@xmission.xmission.com> (raw)
In-Reply-To: <20040320014141.B18D8109A17@earth-ox.its.caltech.edu>
"Stephan T. Lavavej" <stl@caltech.edu> writes:
> Thanks for the reply.
>
> [Gabriel Dos Reis]
> > As you probably know, in the nutshell, native builds on MinGW
> > or Cygwin do not have support for wchar_t so corresponding
> > support in libstdc++ is disabled. It looks like when
> > building the cross, you did -not- take that fact into
> > consideration and somehow requested support for wchar_t while
> > the underlying C functions are missing.
>
> But how did I do that? In my build script, I configure cross binutils,
> cross gcc, and crossed-native gcc with --disable-nls.
>
> Or does that not affect wchar gunk at all?
>
> How can I disable the wchar stuff explicitly?
I think you want to add --disable-c-mbchar to your configure line for
gcc.
See http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html
However I don't have a cygwin system to test this on.
There are two caveats to this flag: (a) it makes a libstdc++ without
wchar support and therefor farther from the ISO standard, and (b) C++
built with a --disable-c-mbchar configured compiler may not be
linkable with code built with a --enable-c-mbchar compiler.
next prev parent reply other threads:[~2004-03-20 2:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 4:53 Stephan T. Lavavej
2004-03-20 5:00 ` llewelly [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 13:59 Stephan T. Lavavej
2004-03-20 5:00 Stephan T. Lavavej
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=s3r65d0b50f.fsf@xmission.xmission.com \
--to=llewelly@xmission.com \
--cc=gcc@gcc.gnu.org \
--cc=stl@caltech.edu \
/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).