SUNWspro/WS6U2/include compilation error

I am using Solaris 2.7 with compiler version: Sun WorkShop 6 update 2 C++
5.3 Patch 111685-06 2002/03/09
I am using -library=rwtools7,iostream and during compilation, I get the
following errors:
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 22: Error:
"virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 22: Error: Use ";"
to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 31: Error: Use ";"
to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./new", line 24: Error: Use ";" to
terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 59: Error:
"virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 59: Error: Use
";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 64: Error: Use
";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 130: Error:
"virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 130: Error:
Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 135: Error:
Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./typeinfo", line 46: Error: Use ";"
to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./typeinfo", line 55: Error: Use ";"
to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 103: Error:
"virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 103: Error: Use
";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 105: Error: Use
";" to terminate declarations.
15 Error(s) detected.
Any ideas?
Thanks,
brett

Below is my compilation command line. I haven't been able to build a small code sampe to reproduce. It only seems to be occuring with the inclusion of all my third party software (Not one alone triggers the error). I was hoping that the error had been seen by somebody before and could point out what may be going on. Thanks for any help.
brett
/usr/Forte/SUNWspro/bin/CC -compat=5 -KPIC -mt -D_REENTRANT -library=rwtools7,iostream -DSUN -DDtDISVERS=5 -DDtHLA=1 -DDtRPR=1 -O -w -c -I/usr/include -I. -I/home/bkaylor/GDUtils/SW/GFCTerrain/include -I/home/bkaylor/GDUtils/SW/GFCUtils/include -I/home/bkaylor/GDUtils/SW/GFCTirem/include -I/home/bkaylor/GDUtils/SW/GFCUtils/include -I/home/bkaylor/GDUtils/SW/GFCVrl/include -I/home/bkaylor/GDUtils/SW/GFCUtils/include -I/home/bkaylor/MaK/makRti1.3.6-ngc/include -I/home/bkaylor/MaK/vrlink3.7-ngc/include -I/home/bkaylor/MaK/logger3.7-ngc/include -I/home/bkaylor/GDUtils/SW/GFCGTO/GTO/Gen -I/home/bkaylor/GDUtils/SW/GFCGTO/XDA/include -I/home/bkaylor/GDUtils/SW/GFCUtils/include -I../../include ../SI.C
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 22: Error: "virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 22: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./exception", line 31: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./new", line 24: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 59: Error: "virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 59: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 64: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 130: Error: "virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 130: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/./stdexcept", line 135: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./typeinfo", line 46: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/./typeinfo", line 55: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 103: Error: "virtual" is not allowed here.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 103: Error: Use ";" to terminate declarations.
"/usr/Forte/SUNWspro/WS6U2/include/CC/Cstd/rw/iosbase", line 105: Error: Use ";" to terminate declarations.
15 Error(s) detected.

Similar Messages

Compilation Error on CC 5.3

Hi,
I,am getting the following compilation error with CC 5.3 (Forte 6 Update 2)
"/opt/SUNWspro/WS6U2/include/CC/memory.h.SUNWCCh", line 26: Error: "memchr" declaration conflicts with "std::memchr(const void*, int, unsigned)" introduced by using declaration.
we are working on porting of an application developed on window to solaris. this application
is using hash_map which CC 5.3 stl is not supporting so we are using STLPort 4.5.1 for this
with CC 5.3 iostreams.
Regards
mahidhar

Hi,
I,am getting the following compilation error with CC 5.3 (Forte 6 Update 2)
"/opt/SUNWspro/WS6U2/include/CC/memory.h.SUNWCCh", line 26: Error: "memchr" declaration conflicts with "std::memchr(const void*, int, unsigned)" introduced by using declaration.
we are working on porting of an application developed on window to solaris. this application
is using hash_map which CC 5.3 stl is not supporting so we are using STLPort 4.5.1 for this
with CC 5.3 iostreams.
Regards
mahidhar

Compilation error with RWTValDlist T find() method

This code used to compile fine with SC 4.x C++ compiler. We are migrating to "Sun WorkShop 6 update 2 C++ 5.3 2001/05/15" and it is now generating the following compilation error:
===============================
cd generic/src; make -f generic.mk
/opt/SUNWspro/bin/CC -c -PIC -compat -library=rwtools7 -O2 -I. -I. -I../include -I/home/jm/sunos5.8/ib_service_3.4.3/include -I/opt/local/megen/include -I/opt/SUNWspro/WS6U2/include/CC -I../../interface/include -I../include -I. -I/home/jm/sunos5.8/acell_4.1/include -I/opt/local/access/home/include -I/home/jm/sunos5.8/acell_4.1/include/packetcpp -I/home/jm/sunos5.8/acell_4.1/include/ecl -I/home/jm/sunos5.8/acell_4.1/include/gels -I/home/jm/sunos5.8/acell_4.1/src/security/include -I/home/jm/sunos5.8/acell_4.1/include/sequencer -I/home/jm/sunos5.8/acell_4.1/include/gen -I/home/jm/sunos5.8/acell_4.1/include/recipeMgr -I/home/jm/sunos5.8/acell_4.1/include/EFEFeature -I/home/jm/sunos5.8/ib_service_3.4.3/include -I/opt/local/megen/include -I/opt/local/rv/include -I/opt/local/etk/include -I/opt/local/etk/include/tdl -DTCPIP=1 -D__SYSVR4 -DSHOP=1 -D_SOLARIS=1 -I/opt/local/std_comp/include ACEAlarmClock.C
"ACEAlarmClock.C", line 479: Error: Could not find a match for RWTValDlist<ACEObject*>::find(int(const ACEObject*&,void*), void**, ACEObject*).
1 Error(s) detected.
*** Error code 1
make: Fatal error: Command failed for target `ACEAlarmClock.o'
===============================
The header file in question is:
#include <rw/tvdlist.h>
class ACEAlarmClock : public ACEObject
// The public interface.
public:
ACEAlarmClock();
// Default constructor.
private:
static void alarmCallback(void *passAheadRef, ib_alarmid alarmId);
static RWTValDlist<ACEObject *> AlarmClocks;
and the source file in question is:
void
ACEAlarmClock::alarmCallback(void *passAheadRef, ib_alarmid alarmId)
ACEObject *object = 0; // returned by find()
if (AlarmClocks.find(findAlarmId, &alarmId, object))
ACEAlarmClock alarmClock = (ACEAlarmClock )object;
if (alarmClock)
AlarmClocks.remove(alarmClock);
alarmClock->isActive_ = FALSE;
alarmClock->onAlarm(passAheadRef, alarmId);
return;
Any help is highly appreciated. Thanks.
Cesar Saavedra
[email protected]

The C++ Migration Guide that comes with the compiler explains in detail everything you to need to know about migrating from C++ 4.2 to C++ 5.3.
Use the "-compat" option on every CC command, compiling and linking. Any code that worked with C++ 4.2 will work the same way with C++ 5.3 in compat mode.
-compat=4 sets language and binary compatibility to that of the 4.x compilers. -compat=5 sets language and binary compatibility to ANSI/ISO standard mode. If the -compat option is not specified, -compat=5 is assumed.
- Rose

Include file error from a new install of C++ compiler on Solaris 5.7

Here is the command line being executed:
CC test.cc
Here is the sample cc file being compiled:
#include <iostream>
int main() {
std::cout << "Real programmers write C++!" << std::endl;
return 0;
Error Output:
"/opt/SUNWspro/WS6/include/CC/std/stddef.h", line 7: Error: Could not open inclu
de file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/std/stddef.h", line 15: Error: Could not open incl
ude file <sys/isa_defs.h>.
"/opt/SUNWspro/WS6/include/CC/std/stdarg.h", line 7: Error: Could not open inclu
de file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/std/string.h", line 7: Error: Could not open inclu
de file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/std/ctype.h", line 7: Error: Could not open includ
e file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/std/wchar.h", line 6: Error: Could not open includ
e file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 34: Error: Could not ope
n include file <sys/isa_defs.h>.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 35: Error: Could not ope
n include file <stdio_tag.h>.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 36: Error: Could not ope
n include file <wchar_impl.h>.
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 7: Error: Could not open include
file <sys/feature_tests.h>.
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 42: Error: Could not open includ
e file <sys/types.h>.
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 52: Error: Could not open includ
e file <sys/time_impl.h>.
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: Type name expected in
stead of "pthread_attr_t".
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: No storage class or t
ype for this declaration.
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 85: Error: "," expected instead
of "*".
"/opt/SUNWspro/WS6/include/CC/std/time.h", line 86: Error: Use ";" to terminate
declarations.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 38: Error: Could not ope
n include file <sys/va_list.h>.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 94: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 95: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 96: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 97: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 98: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 99: Error: __FILE is not
defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 100: Error: __FILE is no
t defined.
"/opt/SUNWspro/WS6/include/CC/wchar_iso_SUNWCC.h", line 152: Error: __FILE is no
t defined.
Compilation aborted, too many Error messages.
Could someone please help with solving this compilation error.
Thanks

Hi there,
I guess a simple modification to your PATH statement would solve this, you can also specify "-I /usr/include" in your makefile as a path to search for. So I only think your environment needs a little twinkling.
M. Poels ([email protected])

How do I add an included jsp to my project and not get a compile error?

Hi,
I have a project with some included jsp's however if I add them to the project, when I build I get a compile error as the jsp uses variables from the calling jsp.
Any ideas on how to get round this.
Thanks
DM

There are two main ways that I deal with this problem (yeah, it sucks, but it sort of makes sense that it happens...) (I presume you're talking static include here...)
#1 - name the included file with an extension that JDev will not try to compile (.jspf - for JSP Fragment - is common) Then it will be compiled in with the including page, but won't gag the project compilation. Advantage - it works, and you find out at compile time if you hosed up the variable reference. Disadvantage: JDev tries really, really, really hard to keep you from naming a JSP file with an extension of .jspf I normally create the .jsp file in JDev, remove it from the project, rename the file outside of JDeveloper, then add it back to the project - pain in the butt, but it works (and you probably aren't building scads of these included files...)
#2 - add the variable to be referenced to the pageContext implicit object as an attribute in your including page (ex, <% pageContext.setAttribute("myVar", myVar); %>), then reference that attribute in your included JSP (ex, <%= pageContext.getAttribute("myVar") %>) . It will compile fine (as the compiler has no way of knowing if the pageContext attribute actually exists, it just sees that the syntax is good and motors along merrily. Advantage: don't have to have differently named JSP files (which isn't actually a big deal). Disadvantage: You hvae to add the variable to the pageContext (and you have to always add Object derivatives, as primitives won't go into a hash) and you don't find out if you screwed the variable up until runtime (when it tries the getAttribute, which could return null if you didn't properly set it to start with) vs at compile-time w/ the direct reference.
HTH!
Jim

ShObjIdl.h compile error when including Photoshop SDK header?

I develop photoshop plugins on both Mac 10.6 and Windows 7, now my code has been built and run successfully on Mac, but on Windows there are curious compile errors in a file "ShObjIdl.h", this is a Windows SDK header file. ( my VC++ version is 2010 ). It seems including some adobe SDK header file will cause the error. Is there someone who had met this? I guess some macro define conflicts.

Sophie
did your program work ok under 10.3.6? Is it just Tiger that gives the problem?
I have not used xmlrpc but I have used Pro*C on OS X with no probelms.
Where did the xmlrpc.h you are using come from? I could not find it on OS X on either Tiger or Panther. However I do find an xmlrpc.cp and a make file so I assume you would include a shared library from it in the make file for your program to be able to make the xmlrpc calls you need to.
In general, the include files are in sub directories of /System/Library/Frameworks and it would be worth a grep -r for the declarations you want to include and put the path in the include parameter to proc.
I hope this info helps.
Paul

Compile Errors occured when simulink models including 'cmex' by SIT

I am trying to compile a simulink model to DLL with following softwares and hardwares.
Software:
LabVIEW 8.0.1
LabVIEW Realtime 8.0.1
Simulation Interface Toolkit 3.0
MATLAB R13
Visual C++ 6.0 Service Pack 4
Target Hardware:
PXI-1042RTPXI-8196
PXI-6289
When I tried to compile a model including 'cmex' function on Simulink to DLL, compile error about Visual C++ occured. Does SIT support the model including 'cmex' functions?
When I removed the function 'cmex', compiling is working correctly.
To import original model which is written by C or other language, I strongly want to use 'cmex' functions. To avoid the compile error, if you have any ideas, please let me know.
Thanks,
Tsugo

Hello Tsugo,
I believe that it is possible to compile a DLL for SIT from a model that contains a cmex function.
To tell whether the issue is caused by SIT or not, you can try changing the RTW target file from nidll.tlc to grt.tlc (in the model's Simulation Parameters dialog, look in the Real-Time Workshop tab), and see whether the compile error still happens. If the compiler error occurs with grt.tlc, then please refer to the documentation provided by The MathWorks Inc. on how to get your cmex functions to work in Real-Time Workshop®.
If the compiler error does not occur with grt.tlc, then please post the whole text of the compiler error.
Thanks!
Andrew

Compilation errors with boost 1.36

Hi,
My compiler
CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-08 2002/06/02
I am getting the followin*g errors when trying to compile
Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 108: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 116: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 122: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 128: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 141: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
"./boost/math/tools/precision.hpp", line 172: Error: Default arguments cannot be added in later declarations of the template function in the same scope.
I have done configuration as following
%> ./configure with-toolset=sun prefix=/u/jn/boost/boost_1_36_0
my usr-config.jam file looks as below
# Boost.Build Configuration
# Automatically generated by Boost configure
# Compiler configuration
using sun : 6 : /home/nfs/sollocal/beatlehome1/F6U2/SUNWspro/bin/CC : <stdlib>sun-stlport
<cxxflags>-library=stlport4 -m64 -xcode=pic32 -erroff=wvarhidemem,hidevf,hidevfinvb -errtag
s=yes <linkflags>-library=stlport4 -m64 ;
# Python configuration
using python : 2.6 : /usr/local ;
my Makefile
BJAM=./tools/jam/src/bin.solaris/bjam
BJAM_CONFIG= -sICU_PATH=/usr
prefix=/u/jnarayan/boost/boost_1_36_0
exec_prefix=$(prefix)
libdir=$(exec_prefix)/lib
includedir=$(prefix)/include
LIBS=
all: .dummy
@echo "$(BJAM) $(BJAM_CONFIG) --user-config=user-config.jam $(LIBS)"
@$(BJAM) $(BJAM_CONFIG) --user-config=user-config.jam $(LIBS) || \
echo "Not all Boost libraries built properly."
clean: .dummy
rm -rf bin.v2
distclean: clean
rm -rf Makefile config.log
check: .dummy
@cd status && ../$(BJAM) $(BJAM_CONFIG) --user-config=../user-config.jam || echo "S
ome Boost regression tests failed. This is normal for many compilers."
install: .dummy
@echo "$(BJAM) $(BJAM_CONFIG) address-model=64 user-config=user-config.jam pref
ix=$(prefix) exec-prefix=$(exec_prefix) libdir=$(libdir) --includedir=$(includedir) $(L
IBS) install"
@$(BJAM) $(BJAM_CONFIG) address-model=64 --user-config=user-config.jam --prefix=$(p
refix) --exec-prefix=$(exec_prefix) --libdir=$(libdir) --includedir=$(includedir) $(LIBS) i
nstall || echo "Not all Boost libraries built properly."
.dummy:
thanks in advance for your help

BOOST cannot be compiled with WS6u2.
The oldest compiler that can build BOOST is Sun Studio 11 (C++ 5.8).
You will have better luck with Sun Studio 12 (C++ 5.9). Both Studio 11 and Studio 12 are free.
Get Sun Studio 12 here:
[http://developers.sun.com/sunstudio/]
Sun Studio 12 requires Solaris 9, 10, or Open Solaris.
If you are running Solaris 8, get Sun Studio 11 instead:
[http://developers.sun.com/sunstudio/products/previous/11/index.jsp]
After installing the appropriate version of Sun Studio, get all current patches for it here:
[http://developers.sun.com/sunstudio/downloads/patches/index.jsp]
Then check Simon's blog for advice on building BOOST with Sun Studio 11 or 12.
[http://blogs.sun.com/sga/category/Boost]

Compile errors with Solaris 5.8 and Studio 11 with latest patches

I asked sa to patch my studio 11, and they applied patches 121023-04, 121015-04, 121017-08, 122142-03, 120761-03, 120760-11 and 122135-02. Then, I compiled my boost_1_33_1 again. It built some, but not all libraries. It stil spit out the following errors. Is this expected?
"/home/vcheng/boost_1_33_1/libs/filesystem/build/../src/operations_posix_windows.cpp", line 126: Error: readdir_r is not a member of file level.
...failed sunpro-C++-action build_sunos/bin/boost/libs/filesystem/build/libboost_filesystem.a/sunpro/debug/operations_posix_windows.o...
sunpro-C++-action build_sunos/bin/boost/libs/wave/build/libboost_wave.a/sunpro/debug/instantiate_cpp_exprgrammar.o
"/home/vcheng/boost_1_33_1/boost/spirit/core/composite/epsilon.hpp", line 76: Error: complex expression not allowed in dependent template argument expression.
"/home/vcheng/boost_1_33_1/boost/iostreams/device/file_descriptor.hpp", line 79: Warning: close_on_exit hides boost::iostreams::file_descriptor::impl::close_on_exit.
1 Warning(s) detected.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 42: Error: BZ_CONFIG_ERROR is not defined.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 106: Error: The function "BZ2_bzCompressEnd" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 107: Error: The function "BZ2_bzDecompressEnd" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 113: Error: The function "BZ2_bzCompress" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 118: Error: The function "BZ2_bzDecompress" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 143: Error: The function "BZ2_bzCompressInit" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/iostreams/build/../src/bzip2.cpp", line 147: Error: The function "BZ2_bzDecompressInit" must have a prototype.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 97: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 100: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 110: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 349: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 383: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 437: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 458: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 477: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/cmdline.cpp", line 495: Warning: args hides boost::program_options::detail::cmdline::args.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/config_file.cpp", line 35: Warning: allowed_options hides boost::program_options::detail::common_config_file_iterator::allowed_options.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 311: Error: Could not find a match for std::count<std::InputIterator, std::T, std::Size>(char*, char*, char) needed in::format_paragraph(std::ostream &, std::string, unsigned, unsigned).
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 378: Error: Too few arguments for template std::reverse_iterator.
"/.automount/opt/Forte/sunstudio11_patch1/SUNWspro/prod/include/CC/Cstd/rw/iterator", line 432: Error: "friend" declaration is incompatible with function template.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 378: Where: While specializing "std::reverse_iterator<const char*>".
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 378: Where: Specialized in non-template code.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 379: Error: Too few arguments for template std::reverse_iterator.
"/home/vcheng/boost_1_33_1/libs/program_options/build/../src/options_description.cpp", line 387: Error: Could not find a match for std::distance<std::ForwardIterator, std::Distance>(const char*, const char*) needed in::format_paragraph(std::ostream &, std::string, unsigned, unsigned).

You can take Boost 1.34 but you have to use CVS and you have to modify Boost configuration files to use -library=stlport4 option.
Or you can take Boost 1.32, read this article http://blogs.sun.com/roller/page/sga?entry=boost_mini_howto and apply this patch http://blogs.sun.com/roller/resources/sga/boost_1_32_0.patch.
As you can see here http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/summary.html Sun C++ is in a good shape.

Compilation error, When moving from 32-bit to 64-bit code

Hello,
I m getting Compilation error, This program already compiled on 32 bit, but getting compilation error on 64 bit.
CC -V
CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
make
Making dependencies...
cc -g -D__EXTENSIONS__ -D_SVID_GETTOD -I../h -I/app/oracle/product/9.2_32/precomp/public -I. -xcg92 `getconf LFS_CFLAGS | head -1` -D UT_TRACE_FUNCTION -Dbool=int -g -D -I. -m64 -xarch=sparcvis -H -w -E 2>&1 >/dev/null Bitmap.cc BitmapData.cc BitmapInputTxnStream.cc BitmapOutputStream.cc UnexpectedException.cc FieldData.cc FieldDataCollection.cc FieldDefinition.cc FieldDefinitionCollection.cc OutputFixedStream.cc ParsingEngine.cc Schema.cc Statistics.cc String.cc TraceStream.cc TxnStream.cc c_api.cc SocketImpl.cc Socket.cc ServerSocket.cc UnixSocket.cc Thread.cc test.cc | grep -v License | grep -v command | ../dvl.bin/mkdep >.depends
Dependencies updated...
CC -g -D__EXTENSIONS__ -D_SVID_GETTOD -I../h -I/app/oracle/product/9.2_32/precomp/public -I. -xcg92 `getconf LFS_CFLAGS | head -1` -D UT_TRACE_FUNCTION -Dbool=int -g -D -I. -m64 -xarch=sparcvis -c Bitmap.cc
"/opt/SUNWspro/prod/include/CC/Cstd/./limits", line 1046: Error: Multiple declaration for std::numeric_limits<int>.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 192: Error: Multiple declaration for std::ostream::operator<<(int).
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 351: Where: While specializing "std::ostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 351: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 192: Error: Multiple declaration for std::wostream::operator<<(int).
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 354: Where: While specializing "std::wostream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 354: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/Cstd/./istream", line 104: Error: Multiple declaration for std::istream::operator>>(int&).
"/opt/SUNWspro/prod/include/CC/Cstd/./istream", line 373: Where: While specializing "std::istream ".
"/opt/SUNWspro/prod/include/CC/Cstd/./istream", line 373: Where: Specialized in non-template code.
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
"RuntimeException.h", line 131: Error: Function RuntimeException::~RuntimeException() can throw only the exceptions thrown by the function std::exception::~exception() it overrides.
"RuntimeException.h", line 97: Error: Could not find std::exception::exception(const char*) to initialize base class.
"RuntimeException.h", line 121: Error: xmsg is not a member of std::exception.
"Bitmap.cc", line 62: Error: Cannot return int(Bitmap::*)()const from a function that should return int.
11 Error(s) detected.
make: *** [Bitmap.o] Error 11
In Makefile CFLAGS setting are as follows,
### Setup common symbols for .depends
SRC = $(TEST_SRC)
INCLUDES = $(TEST_INC)
# clean objects, executeable, generated .pc -> .c
CLEAN = -r *.o $(PGM_EXEC) Templates.DB/* SunWS_cache/*
include $(ROOT)/h/common.mak
# The system include directory must be specifically included first because some of the
# ghost includes use system include file names (e.g., generic.h)
# Modified these section to compile on TVLAPP1HAG
CFLAGS += -D $(STDOUT_TRACE)
CFLAGS += -Dbool=int -g -D$(MAINLINE) $(OUR_COLLECTION)
#CFLAGS += -compat -Qoption ccfe -abirel=4.1
#CFLAGS += -Qoption ccfe -abirel=4.1
CFLAGS += -I. -m64 -xarch=sparcvis
#CFLAGS += -I. -mt
# Add the flag for multi-threaded apps
LDFLAGS += -lsocket -lnsl -lthread
# declare an empty macro for compiler directive flags, to be command-line
# driven (ie, for -D directives)
CCFLAGS=
CCFLAGS += -DRW_NO_CPP_RECURSION
# The following manipulation of CC and overriding the .cc.o suffix
# dependency is removed here to use what is supplied by default int
# the h/common.mak file.
#XX = CC
#CC = CC
#COMPILE = $(CC) -o $*.o $(CFLAGS) $(CCFLAGS) -c $*.cc
#.cc.o:
# $(COMPILE)
Please Help

Hello,
Still I am not able to solve the error. please help me.. Please see the below code...
Error:
s3dvap983:/export/home/pshirode/rel_v95/cc_lib > make
Making dependencies...
cc -g -D__EXTENSIONS__ -D_SVID_GETTOD -I../h -I/app/oracle/product/9.2_32/precomp/public -I. `getconf LFS_CFLAGS | head -1` -D UT_TRACE_FUNCTION -g -D -I. -m64 -xarch=sparcvis -H -w -E 2>&1 >/dev/null Bitmap.cc BitmapData.cc BitmapInputTxnStream.cc BitmapOutputStream.cc UnexpectedException.cc FieldData.cc FieldDataCollection.cc FieldDefinition.cc FieldDefinitionCollection.cc OutputFixedStream.cc ParsingEngine.cc Schema.cc Statistics.cc String.cc TraceStream.cc TxnStream.cc c_api.cc SocketImpl.cc Socket.cc ServerSocket.cc UnixSocket.cc Thread.cc test.cc | grep -v License | grep -v command | ../dvl.bin/mkdep >.depends
Dependencies updated...
CC -g -D__EXTENSIONS__ -D_SVID_GETTOD -I../h -I/app/oracle/product/9.2_32/precomp/public -I. `getconf LFS_CFLAGS | head -1` -D UT_TRACE_FUNCTION -g -D -I. -m64 -xarch=sparcvis -c Bitmap.cc
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/opt/SUNWspro/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
"RuntimeException.h", line 137: Error: Function RuntimeException::~RuntimeException() can throw only the exceptions thrown by the function std::exception::~exception() it overrides.
"RuntimeException.h", line 103: Error: Could not find std::exception::exception(const char*) to initialize base class.
"RuntimeException.h", line 127: Error: xmsg is not a member of std::exception.
"Bitmap.cc", line 62: Error: Cannot return int(Bitmap::*)()const from a function that should return int.
7 Error(s) detected.
make: *** [Bitmap.o] Error 7
96 class RuntimeException : public xmsg {
97 public:
98
99 /**
100 * Create an exception with a simple error message
101 * @param message The error message
102 */
103 RuntimeException(const char* msg) : xmsg(msg) {}
104
105 /**
106 * Create an exception with an error code, fileinfo, and message. This will
107 * produce an error message that looks like:
108 * in File:%s at line#: %d \n %error_message%
109 *
110 * @param error An integer error code. The catch block can use the error()
111 * method to examine this value
112 * @param fileinfo The location in a source file where the error occured
113 * @param msg The error message
114 * @see RuntimeException.error
115 */
116 RuntimeException(int p_error, const Fileinfo& f, const char* msg)
117 {
118 error = perror;
119 strstream buffer;
120 buffer << "in File:"
121 << f.filename()
122 << " at line#:"
123 << f.lineno() << endl << msg
124 << ends; // required for this strstream library, other versions
125 // like Borland the stream is always null terminated
126
127 xmsg::xmsg(buffer.str());
128 delete buffer.str(); // added by db 03-Jul-98 accoprding to the
129 // ssbuf(3C++) man page - other implementations may
130 // use malloc/free but Solaris uses new/delete
131 }
132
133 /** @return the error code */
134 int error() {return _error;}
135
136 /** Clean up instance */
137 virtual ~RuntimeException() {}
138
139
140 protected:
141
142 /**
143 * Default constructor - not very useful to throw an exception without at
144 * least an error message, so this is reserved for only subclasses.
145 */
146 RuntimeException() : xmsg() {}
147
148 private:
149
150 /** the error code associated with the error */
151 int _error;
152 };
153

Compilation error with sun workshop 6u2

hi,
i try to compile a systemc code with sun work shop 6u2 but the compilation generate this error
Beginning generate/compile...
Compilation may take a few seconds... please wait.......ucbcc: Warning: Option -YP,:/usr/ucblib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin/../lib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin:/usr/ccs/lib:/usr/lib passed to ld, if ld is invoked, ignored otherwise
ucbcc: Invalid input file name /home/uei/chtourou/cadence/soflib/fir/pmb/spb.C, no output generated for this file.
ucbcc: Warning: Option -YP,:/usr/ucblib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin/../lib:/usr/ensta/pack/SunWorkShop-6u2/SUNWspro/WS6U2/bin:/usr/ccs/lib:/usr/lib passed to ld, if ld is invoked, ignored otherwise
ld: warning: option -YP appears more than once, first setting taken
ld: fatal: file /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.o: cannot open file: No such file or directory
ld: fatal: File processing errors. No output written to /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.so
system-002: Error: The following system command failed.
CC -G -o /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.so /home/uei/chtourou/cadence/soflib/fir/pmb/spb_sun4v.o `/home/uei/chtourou/tmp/systemc-2.0.1/spwSystemC/src/libList.csh.${PLATFORM_DIR}` -lc
leaf-057: Error: Failed to compile the SPB wrapper for polymorphic leaf
soflib/fir.pmb
Failed SPB Wrapper generation for soflib/fir with 2 Error(s), 0 Warning(s) and 0 Note(s).
Compilation Failed .
thank you very much

this compilation it's made from cadence spw and it use the sun workshop,so i don't know options of compilation
my os is the SUNOS 5.8
any help will be usefull
thank you

Compilation Error with Solaris8

Hi ,
I am getting a queer compilation error when compiling a simple C++ program on
Solaris8 . The error does not occur with solaris7 . I have inclued the program
and the error message . Can you give me some tips to overcome this problem .
#include <iostream.h>
int main ( void)
cout << "hello world" ;
/*************COMPILATION ERRROS ***************/
"/usr/include/iso/wchar_iso.h", line 100: Error: Multiple declaration for mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 51: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 78: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/rw/iotraits", line 56: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
4 Error(s) detected.
Regards,
vichu

Thanks! However, my sample code does not inclide iostream.
#include <string>
main() {
string s = "123asd";
exit(0);
and there is the output
hwang@jazz: /opt/SUNWspro/SC5.0/bin/CC test.C
"/usr/include/wchar_impl.h", line 24: Error: Multiple declaration for __mbstate_t.
"/usr/include/wchar.h", line 90: Error: Multiple declaration for mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 37: Error: The name __mbstate_t is ambiguous,
__mbstate_t and __mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 45: Error: Multiple declaration for mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/rw/iotraits", line 37: Error: The name __mbstate_t is ambiguou
s, __mbstate_t and __mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/rw/iotraits", line 57: Error: Multiple declaration for mbstate
_t.
"test.C", line 4: Error: string is not defined.
"test.C", line 4: Error: Cannot use const char* to initialize int.
8 Error(s) detected.
Any ideas?
Thanks again

Studio 11 compiler error - SunIR version

I am trying to recompile my code after installing sun studio 11, but am getting compilation errors. If I compile my code using
f90 -KPIC -C -e -u -v -r8const mengmr5.f -c -O2
My files seem to compile ok. If instead I use
f90 -KPIC -C -e -u -v -r8const mengmr5.f
(without -O2) I get the following
### command line files and options (expanded):
### -xcode=pic32 -C -e -u -v -r8const mengmr5.f -c
### f90: Note: NLSPATH = /ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/f90comp -y-o -ymengmr5.o -N132 -ev -eI -y-ftrap=common -m3 -dq -y-fbe -y/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/fbe -y-xarch=generic -H "/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/bin/f90 -KPIC -C -e -u -v -r8const -c " -y-xcache=generic -xcache=generic -I/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/include/f95/v8 -p/ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/lib/modules -y-verbose -RM -xall -y-PIC -PIC -y-xcode=pic32 -xmemalign=8i -y-xmemalign=8i -r8const -y-xdbggen=no%dwarf2+stabs -xassume_control=optimize -y-xassume_control=optimize -iorounding=processor-defined -xhasc=yes mengmr5.f
Build problem: Yabe expected SunIR version 7.0.0; got 7.1.3
Studio 11 is installed in /ford/thishost/unix/loc/studio11/opt/SUNWspro, which I added to my path. I also have LD_LIBRARY_PATH as /ford/thishost/unix/loc/studio11/opt/SUNWspro/prod/lib:/ford/thishost/unix/loc/studio11/opt/SUNWspro/lib:/usr/local/lib:/usr/dt/lib:/usr/lib:/usr/openwin/lib:/usr/4lib:/usr/sfw/lib:/usr/share/lib:/usr/local/link/lib:/ford/thishost/u/Tools/SunOS/5.8/lib:/ford/thishost/u/Tools/SunOS/5.8/lib
If I build optimized, I have problems debugging as I cannot see values in optimized functions. Is there a way to fix this?

Try unsetting your LD_LIBRARY_PATH.
You should not need it.
If it is not that,
then you probably have some problem with your installation
of the compilers.
Check the installation logs and any patch logs for clues.
Peter.
-pd 2/22/06

Studio 8 compiler error using rogue wave header in std mode

I get the following compiler error. I am using -library=rwtools7_std in the CC command.
The error is:-
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The name istream is ambiguous, istream and std::istream.
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The name istream is ambiguous, istream and std::istream.
"/opt/studio/SUNWspro/prod/include/CC/rw7/rw/rstream.h", line 46: Error: The type "istream" is incomplete.
Please help
Kandiah

All,
I'm getting the following error when I moved to Rogue Wave release 7.0 from 4.0. We're using Sun's FORTE C++ compiler version 7.0.
Please advise
*** Build for src 'all' target STARTED: Thu Jan 18 16:37:04 EST 2007
/xenv/Forte/sun4/7.0/5.8p4/prod/bin/CC -g -features=no%conststrings -DCPLUSREL=7 -D_RWCONFIG=12d -DRW_MULTI_THREAD -O -mt -D_REENTRANT -c -I. -I/xenv/rwsp_tools/sun4/5.8p4/7.0/32/core900_12d -I/xenv/mqi/sun4/5.x/5.3.0.5/inc -I/xenv/ccs_standard_s8/sun4/5.8p4/4.1_B1/include MQInfo.cc MQBase.cc ZeusAccountBridge.cc
MQInfo.cc:
MQBase.cc:
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/stringid.h", line 50: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/stringid.h", line 51: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/collint.h", line 75: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/collint.h", line 76: Error: A typedef name cannot be used in an elaborated type specifier..
7 Error(s) detected.
ZeusAccountBridge.cc:
"/xenv/ccs_standard_s8/sun4/5.8p4/4.1_B1/include/ccs_data.h", line 126: Warning (Anachronism): Using int(*)(void*,ccs_Data*) to initialize void*.
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 316: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 317: Error: A typedef name cannot be used in an elaborated type specifier..
"/xenv/Forte/sun4/7.0/5.8p4/prod/include/CC/rw7/rw/defs.h", line 318: Error: A typedef name cannot be used in an elaborated type specifier..
3 Error(s) and 1 Warning(s) detected.

Compilation error after installing Sun patches

hello,
One of our customer installed teh following Sun patches:
119254-73
124867-14
124863-23
124870-03
124872-07
126495-04
126995-04
127000-13
127001-04
127143-03
118683-05
119963-20
120753-08Now when they compile the application they get the following error:
cd /usr/opt/temip/mmtoolkit/examples/
make -f temip_ef_user_library.make
/opt/SUNWspro/bin/CC -c -m64 -xcode=pic32 -g -xO0 -D_POSIX_PTHREAD_SEMANTICS -mt -pto -I/usr/opt/temip/tfc/include -I//usr/opt/temip/mmtoolkit/include -I//usr/opt/temip/acloc/include -I//usr/opt/temip/ocs/include -D_RWCONFIG_m -o temip_ef_user_library.o temip_ef_user_library.cxx
**"/opt/SUNWspro/prod/include/CC/Cstd/rw/traits", line 535: Error: The function "wcsstr" must have a prototype.*
*1 Error(s) detected.
*** Error code 1
The following command caused the error:
`echo "/opt/SUNWspro/bin/CC -c -m64 -xcode=pic32 -g -xO0 -D_POSIX_PTHREAD_SEMANTICS -mt -pto -I/usr/opt/temip/tfc/include -I//usr/opt/temip/mmtoolkit/include -I//usr/opt/temip/acloc/include -I//usr/opt/temip/ocs/include -D_RWCONFIG_m " | sed 's/[ ][ ]*/ /g'` -o temip_ef_user_library.o temip_ef_user_library.cxx
make: Fatal error: Command failed for target `temip_ef_user_library.o'
does anyone has an idea ?
thank you for your help.
regards,
Christine

Notes for future posting:
1. When you have a question about patches, please also provide the one-line patch description. Otherwise, anyone who might be inclined to help first has to look them up. Making volunteers do extra work to help you for free is not the best strategy. 119254-73 Install and Patch Utilities Patch (unlikely to affect compiling programs)
124867-14 Patch for C 5.9 compiler (unlikely to affect C++ compiling)
124863-23 Patch for Sun C++ 5.9 Compiler (Aha!) <-----------
124870-03 Patch for Sun Performance Library (unlikely to affect compiling programs)
124872-07 Patch for dbx 7.6 Debugger (unlikely to affect compiling programs)
126495-04 Patch for debuginfo handling (unlikely to affect compiling programs)
126995-04 Patch for Performance Analyzer Tools (unlikely to affect compiling programs)
127000-13 Patch for Fortran 95 8.3 Compiler (unlikely to affect C++ compiling)
127001-04 Patch for Fortran 95 8.3 Dynamic Libraries (unlikely to affect compiling programs)
127143-03 Patch for Fortran 95 8.3 Support Library (unlikely to affect compiling programs)
118683-05 Patch for profiling libraries and assembler (could possibly affect compiling C++) <----------
119963-20 Shared library patch for C++ (unlikely to affect C++ compiling)
120753-08 Microtasking libraries (libmtsk) patch (unlikely to affect compiling programs)If you had gone through this exercise, you could have eliminated many of these patches from consideration. For example, a Fortran runtime library patch or a dbx patch cannot cause the C++ compiler to generate a compile-time error that it did not generate before.
2. Put all source code and error messages in "code" tags, as you did with the list of patches. The non-alphanumeric characters in source code and messages can be interpreted as formatting directives instead of being displayed. The result is often nonsense or is hard to read.
Notes on the command line:
1. The -xO0 option is not supported, and has unpredictable results. If you do not want optimization because you want to debug the code, use either no -xOn option, or use -xO1. Using no option is generally preferred: compilation is faster, and the generated code is usually better than with -xO1.
2. The -pto (-instances=static) option is generally a really bad idea. Unless you have a specific reason why you need this template compilation mode, you should remove the -pto option from all command lines (to use the default -instances=global mode), delete all your binaries, and rebuild the application.
Neither of these problems causes the error message, however.
What could be wrong
Also on the command line is a macro definition that appears to be -D_RWCONFIG_m
Is that the correct rendering of the option? If not, please show the command line again inside "code" tags.
I'm concerned that you are trying to override a configuration macro for libCstd, the C++ runtime library. Doing so is not supported and has unpredictable results. If -D_RWCONFIG_m is what is really on the command line, it will not cause a problem with the library.
Except for the possible macro definition issue, finding the problem will require looking at the source code. Since the error message refers to one of the compiler's own headers, the most likely possibilities are
1. A bug in the headers that might be fixed in a later patch -- 124863-23 is not the most recent patch.
2. An error in your code that worked only by accident before. I'm thinking of an inappropriate macro definition.
If you strip everything out of the temip_ef_user_library.cxx file after all the #include directives, you should be able to compile the resulting file and see the same error message. If so, please post that small file here (inside "code" tags).

SUNWspro/WS6U2/include compilation error

Similar Messages

Maybe you are looking for