C++ Application on HP-UX aCC : STL issue

[nsarkar]

Hello Friends,

We are using HPU (B.11.23 U 9000/800 908196403), and aCC (HP ANSI C++
B3910B A.03.70), and it is regarding a warning we got at the time of
compiling our C++ Application.

----------------------
Warning 849: Exact position unknown; near ["MyAppMgr.cpp", line 15]. #
External symbol too long, truncated from 4185 to 4000
bytes,erase__Q2_4__rw9__rb_treeXTQ2_3std12basic_stringXTcTQ2_3std11char_traitsXTc
_TQ2_3std9allocatorXTc__TQ2_3std4pairXTCQ2_3std12basi...
----------------------

We are using STL in our Code. After searching in internet, we got
similar type of message, which described it as mangled name issue,
which is too long for aCC.
<http://groups.google.com/group/comp.lang.c++/browse_thread/thread/
dc68cfa6b174c43f/4b74f15af7ba1620?q=%22External+symbol+too+long,
+truncated+from%22&rnum=1#4b74f15af7ba1620>

Some workaround is there, but that is very odd, and may have some
fatal issue.

I want to know, if anybody has any recommendation regarding this, and
whether it is a genuine aCC compiler issue and HP has some fix of
this.

Thanks in advance.
Regards,
Nilanjan

 

[=?ISO-8859-1?Q?Erik_Wikstr=F6m?=]

Hello Friends,

We are using HPU (B.11.23 U 9000/800 908196403), and aCC (HP ANSI C++
B3910B A.03.70), and it is regarding a warning we got at the time of
compiling our C++ Application.

----------------------
Warning 849: Exact position unknown; near ["MyAppMgr.cpp", line 15]. #
External symbol too long, truncated from 4185 to 4000
bytes,erase__Q2_4__rw9__rb_treeXTQ2_3std12basic_stringXTcTQ2_3std11char_traitsXTc
_TQ2_3std9allocatorXTc__TQ2_3std4pairXTCQ2_3std12basi...
----------------------

We are using STL in our Code. After searching in internet, we got
similar type of message, which described it as mangled name issue,
which is too long for aCC.
<http://groups.google.com/group/comp.lang.c++/browse_thread/thread/
dc68cfa6b174c43f/4b74f15af7ba1620?q=%22External+symbol+too+long,
+truncated+from%22&rnum=1#4b74f15af7ba1620>

Does it say anything about what might happen if you get this warning,
remember that it is a warning, it does not have to mean that something
is wrong. For certain usages this might be ignorable.

Some workaround is there, but that is very odd, and may have some
fatal issue.

I want to know, if anybody has any recommendation regarding this, and
whether it is a genuine aCC compiler issue and HP has some fix of
this.

For issues with aCC you should ask in a group discussing aCC,
implementation specific questions are off-topic in here.