Re: [reSIProcate] Solaris and STL implementations
This sounds a lot like a case I had a couple of months ago. I needed to
use the resip DNS code in another SIP stack we already had. The rest of
our code uses RogueWave, while resip just uses STL as you mention. At
first I built them separately and linked them together (we use static
links). The link worked fine as long as I linked in both the RW libs
and -lstdc++, but it crashed at runtime.
I had to build resip with RogueWave to get it to run. Luckily the only
problems were with the include files. Evidently the RW versions of the
includes don't include as many other includes as STL, so I had to
include them myself. With any luck your case may not be much different.
Search the archives here for my thread called "Extreme link problem" for
more about the hurdles I had to get over. If you have a look at
build/Makefile.pkg you'll see how they do conditional compiles, define
symbols, link in other libs, etc. Their design makes that pretty easy.
Dave
-----Original Message-----
From: Bradley Gorman [mailto:bgorman@xxxxxxxxxxx]
Sent: Friday, March 09, 2007 2:03 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Solaris and STL implementations
Hi All
I'm attempting to use reSIP on Solaris with some existing libraries.
Unfortunately reSIP uses STLport4 while the rest of my catalogue uses
Cstd. Some reading has shown these STL implementations are mutually
exclusive, so I am attempting to port reSIP to Cstd (porting our library
catalogue to STLport4 could prove impossible). My attempts have
generally been met with heap corruption and somewhat random core dumps
(usually on mallocs or mutexes). I'm using Solaris 8 and the Sun Studio
11 compiler.
Has anyone had any luck trying to port reSIP to the Solaris Cstd?
Any advice would be appreciated.
Thanks
Brad