From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16632 invoked by alias); 1 May 2003 10:56:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 16618 invoked by uid 71); 1 May 2003 10:56:01 -0000 Date: Thu, 01 May 2003 10:56:00 -0000 Message-ID: <20030501105601.16617.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Technical Support Subject: Re: libstdc++/10535 Reply-To: Technical Support X-SW-Source: 2003-05/txt/msg00014.txt.bz2 List-Id: The following reply was made to PR libstdc++/10535; it has been noted by GNATS. From: Technical Support To: "'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