Re: [reSIProcate] Compilation error

[Alan Hawrylyshen <alan@xxxxxxxxxx>]

On Tue, Apr 25, 2006 at 10:57:44AM -0700, Karl Mutch wrote:
> Purely off the top of my head ... These errors are occuring possibly for two 
> reasons :
>  
> You might want to investigate new style casts for C++ such as const_cast.
>  
> The const modifier result may not be what the original author intended.  
> Decls and Modifiers are read by compilers right to left, this means that the 
> const is very possibly in the wrong place. Move the const modifier into the 
> decl as appropriate so that when reading right to left it matches the 
> contract of the method as best as you can factor from the body of the method.
>  
> Repost if it continues to go funky.

> 
>       Thank you.  The README file mentions this issue with version 4.  I set 
> the 
>       CC and CXX variables to point to an earlier version and I no longer 
> have 
>       those errors from before.  However, I still have the following errors: 
> 
[snip]
>          resip::Data&, const resip::Data&, bool) const': 
>       Security.cxx:321: invalid conversion from `unsigned char**' to `const 
>       unsigned 
>          char**' 

Without reading too deep, you may be having problems with the version of 
OpenSSL you are using.
Check that it is not too new (or too old). (Post your version to the list).

We generally don't recommend using the released 0.9.0 resiprocate stack. The 
head of SVN is MUCH more recent and stable. A new release should happen some 
time in the next month or so.

Thanks
Alan Hawrylyshen