public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Technical Support <support@isiuk.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10535
Date: Thu, 01 May 2003 10:56:00 -0000 [thread overview]
Message-ID: <20030501105601.16617.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/10535; it has been noted by GNATS.
From: Technical Support <support@isiuk.com>
To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: libstdc++/10535
Date: Thu, 1 May 2003 11:54:18 +0100
James Bannon
Again posting from work.
Having read Wolfgang's reply in the update, I recall seeing a message saying
"checking for wchar_t ... no" appear during the boostrap procedure.
Unfortunately, I don't have a copy of config.log (it was late last night and
I deleted it!). I will try again!
1. Uninstall Cygwin & re-install.
2. Check /usr/include contains wchar.h & that the contents appear sane
(no macros getting in the way).
3. Check that I can use a couple of the functions as well.
4. Check my INCLUDE environment variable. I am a bit suspicious about
this as /usr/include doesn't appear in the definition but most of the MSVC
stuff does. I will
redefine it so that it *only* contains a reference to /usr/include
to eliminate the possibility that configure is looking in the MSVC
directories & can't find wchar.h.
I will also check the value of LIB as well.
5. Run the build again (this time saving all the logs!).
6. Run my tests again.
7. If they fail, I'll try defining the _GCPPLIB_USE_WCHAR_T and
_GCPPLIB_HAVE_WCHAR_T macros in c++config.h or on the command line if I
can't
define them there.
8. I will also try a build for MinGW to see if I get the same results.
If all this fails, I'll send in the config.log. Otherwise I'll update the
case as closed.
Incidentally, a very similar problem (almost identical in fact) is reported
for Sun and HP-UX as I discovered this morning when I searched the GNATS
database again.
Best Regards,
James Bannon
next reply other threads:[~2003-05-01 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 10:56 Technical Support [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 0:16 libstdc++/10535 Wolfgang Bangerth
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=20030501105601.16617.qmail@sources.redhat.com \
--to=support@isiuk.com \
--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).