public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10535
Date: Thu, 01 May 2003 00:16:00 -0000 [thread overview]
Message-ID: <20030501001601.31144.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/10535; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: "james.bannon" <james.bannon@ntlworld.com>
Cc: gcc-gnats@gcc.gnu.org, Begin-cpp <begin-cpp@accu.org>
Subject: Re: libstdc++/10535
Date: Wed, 30 Apr 2003 19:11:35 -0500 (CDT)
> Sorry to mail you direct but the GNATS mailer seems to be broken as I keep
> getting bounce messages.
That's ok for gcc-prs and nobody@... It's a brokenness in GNATS. If you
want something to be appended to a report, you will also have to have a
subject line like the one above.
Regarding all the rest: I don't think I can be of any help here,
unfortunately, not having any knowledge of cygwin or gcc internals. My
best guess is that wide chars are disabled in your installation since the
configure script detected something so it thought wide characters don't
exist (or don't work) on your system. It would then simply switch off
everything that has to do with wchar_t etc. So I think the only advice I
can give is: try to go through the output of configure and see whether
there's something related. Usually, it looks like
checking for wchar_t... no
To find out why it got the negative answer, you may look at the test that
was actually performed in config.log.
Sorry to be of no more help, regards
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-05-01 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 0:16 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 10:56 libstdc++/10535 Technical Support
2003-05-01 0:16 libstdc++/10535 Wolfgang Bangerth
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=20030501001601.31144.qmail@sources.redhat.com \
--to=bangerth@ices.utexas.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).