You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Ravi Inampudi <in...@roguewave.com> on 2006/03/17 00:26:34 UTC
Problem building rwstd Sol8/studio10
Here is the error a customer is having when compiling using Solaris 8 and
Sun Studio 10 with Rogue Wave Std (Source Pro ed 8):
CC -O -D_RWCONFIG=12d -I./../../../include -I./../../..
-I/home2/sunle/chau/RWSrcPro8_BuildSpace_SOL/source/stdlib -I. -D
_RWBUILD_std -O -mt -PIC -library=%none -c
/home2/sunle/chau/RWSrcPro8_BuildSpace_SOL/source/stdlib/ti_winsert_ptr.cpp
"./../../../include/rw/_ioinsert.cc", line 160: Error: Could not find a
match for __rw::__rw_sputn<__rw::_CharT, __rw::_T
raits>(std::wostream, const char*, int, __rw::__rw_true_t) needed in
__rw::__rw_insert<wchar_t, std::char_traits<wchar_t>
, char>(std::wostream &, const char*, int, int).
"./../../../include/rw/_ioinsert.h", line 212: Where: While
instantiating "__rw::__rw_insert<wchar_t, std::char_trait
s<wchar_t>, char>(std::wostream &, const char*, int, int)".
"./../../../include/rw/_ioinsert.h", line 212: Where: Instantiated from
non-template code.
"./../../../include/rw/_ioinsert.cc", line 164: Error: Could not find a
match for __rw::__rw_sputn<__rw::_CharT, __rw::_T
raits>(std::wostream, const char*, int, __rw::__rw_true_t) needed in
__rw::__rw_insert<wchar_t, std::char_traits<wchar_t>
, char>(std::wostream &, const char*, int, int).
"./../../../include/rw/_ioinsert.h", line 212: Where: While
instantiating "__rw::__rw_insert<wchar_t, std::char_trait
s<wchar_t>, char>(std::wostream &, const char*, int, int)".
"./../../../include/rw/_ioinsert.h", line 212: Where: Instantiated from
non-template code.
2 Error(s) detected.
*** Error code 2
make: Fatal error: Command failed for target `ti_winsert_ptr.o'
I did not have any problem building inhouse with this uncertified
configuration; however, the customer is running into this error. Any
comments on what might be going on?
Thanks,
Ravi
-----Original Message-----
From: Jeremy Dean [mailto:dean@roguewave.com]
Sent: Thursday, March 09, 2006 10:27 AM
To: 'stdcxx-dev@incubator.apache.org'
Subject: Problem with AIX/xlC8.0
When trying to build, I am getting the following severe error:
xlCcore_r -q32 -D_RWCONFIG=rms -I./../../../include
-I./../../../include/ansi -I./../../.. -I.. -I. -D_RWBUILD_std -O
-D_REENTRANT -qsuppress=1500-029 -qrtti=all
-qtemplateregistry=libstdrms.tempreg -qsuppress=1540-0183 -c
../ti_money_get.cpp
"./../../../include/streambuf", line 283.43: 1540-0062 (S) The incomplete
class "_Traits" must not be used as a qualifier.
I am building on AIX 5.3 with the xlC++ 8.0 compiler.
Jeremy
Jeremy Dean
Rogue Wave Software,
A QUOVADX(tm) division
Technical Support
Phone: 303-545-3205 -- 1-800-404-4767
E-mail: support@roguewave.com <ma...@roguewave.com>
Web: http://www.roguewave.com/support <http://www.roguewave.com/support>
Knowledge Base entries:
http://www.roguewave.com/kbdocs/search.html
<http://www.roguewave.com/kbdocs/search.html>
View issues online at:
http://www.roguewave.com/youraccount/login/
<http://www.roguewave.com/youraccount/login/>
Re: Problem building rwstd Sol8/studio10
Posted by Martin Sebor <se...@roguewave.com>.
Ravi Inampudi wrote:
> Here is the error a customer is having when compiling using Solaris 8 and
> Sun Studio 10 with Rogue Wave Std (Source Pro ed 8):
>
> CC -O -D_RWCONFIG=12d -I./../../../include -I./../../..
> -I/home2/sunle/chau/RWSrcPro8_BuildSpace_SOL/source/stdlib -I. -D
> _RWBUILD_std -O -mt -PIC -library=%none -c
> /home2/sunle/chau/RWSrcPro8_BuildSpace_SOL/source/stdlib/ti_winsert_ptr.cpp
> "./../../../include/rw/_ioinsert.cc", line 160: Error: Could not find a
> match for __rw::__rw_sputn<__rw::_CharT, __rw::_T
> raits>(std::wostream, const char*, int, __rw::__rw_true_t) needed in
> __rw::__rw_insert<wchar_t, std::char_traits<wchar_t>
> , char>(std::wostream &, const char*, int, int).
[...]
> I did not have any problem building inhouse with this uncertified
> configuration; however, the customer is running into this error. Any
> comments on what might be going on?
It looks like a compiler bug but I don't see anything like it
in our bug database. I would check to see if you are using the
exact same compiler version down to the patch number as the
customer.
Martin