This is the mail archive of the
mailing list for the libstdc++ project.
Re: problems with std::wstring on Solaris
- From: Phil Edwards <phil at jaj dot com>
- To: Anthony Feick <afeick at hotmail dot com>
- Cc: bkoz at redhat dot com, libstdc++ at gcc dot gnu dot org
- Date: Fri, 30 Aug 2002 14:06:29 -0400
- Subject: Re: problems with std::wstring on Solaris
- References: <F44yzC7qxx15Gk97jXl0001ef18@hotmail.com>
On Thu, Aug 22, 2002 at 12:36:19PM -0500, Anthony Feick wrote:
> I assume you're talking about PR 6702 :
Probably 4764 instead.
> When I did that and tried to recompile libstdc++, I had problems with
> iswblank, vfwscanf, vswscanf, vwscanf, and wcstof. (Probably the reason
> GLIBCPP_USE_WCHAR_T was off.) After I commented those out in
> gcc-3.2/libstdc++-v3/include/c_std/std_cwchar.h and
> gcc-3.2/libstdc++-v3/include/c_std/std_cwctype.h libstdc++ compiled and
> installed fine.
Sounds like 4764, all right.
I will try and get gcc building on my Solaris boxes, next time one of them
has some spare cycles, and tweak the tests in acinclude.m4. No promises on
when this might happen.
> Unfortunately, now basic_string::push_back gives a Segfault wmemset () from
> /usr/lib/libc.so.1. I assume this means I am now doing something
> incompatible with the system libraries.
Possibly due to the -fshort-wchar thingy, which you guys ahve already
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002