Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Post by Sami Kukkone » Fri, 03 Jan 1997 04:00:00



        I'm compiling the Rogue Wave Standard C++ Library 1.2 straight
        out of the box using SPARCompiler 4.1 on Solaris 2.5. I get a fair
        amount of compiler errors.

        Rogue Wave tech support hasn't gotten back to me yet so I'm
        wondering if anyone else has compiled it succesfully without
        extensive source modifications?

        Specifically, some typedefs (like argument_type in class unary_compose)
        seem to baffle the compiler as if it couldn't handle the scope
        properly.
--
Everything in this article is factual, and any resemblance to actual persons,
places or organizations living, dead or drunk, is purely intentional.

 
 
 

Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Post by Bryan Altha » Sat, 04 Jan 1997 04:00:00


:
:         I'm compiling the Rogue Wave Standard C++ Library 1.2 straight
:         out of the box using SPARCompiler 4.1 on Solaris 2.5. I get a fair
:         amount of compiler errors.
:
RW's Standard C++ Library is *NOT* supported under Solaris using
SPARCompiler 4.1.  Nor do I think the soon to been released SparcCompiler
4.2 will work with it.  RW's Standard C++ Library requires a more ANSI C++
type compiler, support for additions to template,. etc., and SunSoft is
making little attempt to come out with an ANSI C++ compiler.

:  Rogue Wave tech support hasn't gotten back to me yet so I'm
:  wondering if anyone else has compiled it succesfully without
:  extensive source modifications?
:
No.  If it was that easy, RW would do it themselves.  The sales people
will tell you that the Standard C++ library is not available for Solaris.
It's also not available for HP-UX, but HP is coming out with an ANSI
C++ compiler and bundling RW's Standard C++ library.

Now why can't SunSoft do this?

:  Specifically, some typedefs (like argument_type in class unary_compose)
:  seem to baffle the compiler as if it couldn't handle the scope
:  properly.

 
 
 

Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Post by Greg Come » Sat, 04 Jan 1997 04:00:00




>:
>:         I'm compiling the Rogue Wave Standard C++ Library 1.2 straight
>:         out of the box using SPARCompiler 4.1 on Solaris 2.5. I get a fair
>:         amount of compiler errors.
>:
>RW's Standard C++ Library is *NOT* supported under Solaris using
>SPARCompiler 4.1.  Nor do I think the soon to been released SparcCompiler
>4.2 will work with it.  RW's Standard C++ Library requires a more ANSI C++
>type compiler, support for additions to template,. etc., and SunSoft is
>making little attempt to come out with an ANSI C++ compiler.

>:  Rogue Wave tech support hasn't gotten back to me yet so I'm
>:  wondering if anyone else has compiled it succesfully without
>:  extensive source modifications?
>:
>No.  If it was that easy, RW would do it themselves.  The sales people
>will tell you that the Standard C++ library is not available for Solaris.
>It's also not available for HP-UX, but HP is coming out with an ANSI
>C++ compiler and bundling RW's Standard C++ library.

>Now why can't SunSoft do this?

>:  Specifically, some typedefs (like argument_type in class unary_compose)
>:  seem to baffle the compiler as if it couldn't handle the scope
>:  properly.

We were not aware of the situation being so dire as per above.
You may want to consider Comeau C++ 4.0 Pre-release.
It is very up to date and is being offered for $50.
It's main limitation is a lack of standard library, however
this is exactly what RW is offering.
You may want to check out our web page for what we have available.

- Greg
--
       Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418-3214
               Producers of Comeau C++ 4.0 front-end pre-release
****WEB: http://www.comeaucomputing.com / Voice:718-945-0009 / Fax:718-441-2310

 
 
 

Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Post by Mukesh Kapo » Sat, 04 Jan 1997 04:00:00


RogueWave has released stdlib 1.2.1 and this is compilable with Sun's C++ 4.2
compiler. This version of stdlib does not contain iostreams. It consists of: bitset,
complex, limits, stdexcpt, stl and string. You can get this library directly from
RogueWave.

Mukesh Kapoor

C++ Compiler group,
Sunsoft, Developer Products

 
 
 

Rogue Wave Standard C++ Library 1.2 and SPARCompiler C++ 4.1

Post by David Nels » Sat, 04 Jan 1997 04:00:00


There are other C++ compilers available for Solaris that are closer to
the C++ draft. You might want to try KAI C++. A free 30 day trial
license is available. Check out our web site, http://www.kai.com for
more information and to download the compiler. It comes with a
"Standard" C++ library, but you are free to use your own.

--
#include <std/disclaimer.h>              Kuck and Associates

http://www.kai.com/C_plus_plus           Champaign, IL   61820
KAI C++ - Cross Platform C++ Compiler    (217) 356-2288

 
 
 

1. Rogue Wave 6.0.4, Sun C++ 4.1, Solaris 2.4 -- link problem

Hi,
just installed the SparcWorks C++ 4.1 on a Solaris 2.4 sparc 20 and
attempted to build a program that uses Rogue Wave strings--I get a
consistent link error:

 Undefined                   first referenced
  symbol                         in file
 _ex_keylock                     /opt/SUNWspro/SC4.0/lib/librwtool.a(cstring.o)
 ld: fatal: Symbol referencing errors. No output written to example1

This is using their standard makefile.  My own one liner won't compile
either as long as I use RWCString.  We don't have the RW sources.
What gives?

Terry

--
It is now safe to turn off your computer.

2. MAC address, how to set?

3. Compile c++ program with Rogue Wave libraries?

4. 103612-33 (Solaris 2.5.1 libc etc. patch) breaks nis_cachemgr?

5. A question on the Rogue Wave C++ class library

6. Any suggestion on a good log scanner

7. gdb with SPARCompiler C++ 4.1

8. X send render error when opening file in Konsole

9. SPARCompiler C++ 4.1 Templates DB

10. SPARCompiler C++ 4.1 Templates-cont

11. Using SPARCompiler C++ 4.1 and problems with the <vector> header...

12. SPARCompiler C++ 4.1 Templates Instantiation looping (forever?)

13. SPARCompiler C++ 4.1 's BUG?