compiling shibsp 2.5.1 on solaris: breakdown at the last few steps

[Christopher Bongaarts]

On 2/15/2013 10:38 AM, Uwe Reh wrote:
> Am 15.02.2013 17:13, schrieb Christopher Bongaarts:
>
> OK, with the formated output is the difference more obvious.
> libshibsp.so:
>> bool xmltooling::AbstractPKIXTrustEngine::validate(x509_st*,stack_st*,const xmltooling::CredentialResolver&,xmltooling::CredentialCriteria*)const
> libxmltooling.so:
>> bool xmltooling::ExplicitKeyTrustEngine::validate(x509_st*,stack_st_X509*,const xmltooling::CredentialResolver&,xmltooling::CredentialCriteria*)const
>
> But why is the signature of the method different between the reference
> in libshibsp.so and the implementation in libxmltooling.so?
 >
> BTW. should 'stack_st*' and 'stack_st_X509*' be compatible?

No - it seems like you built libxmltooling and libshibsp against 
different versions of OpenSSL.  If OpenSSL has DEBUG_SAFESTACK defined, 
it uses "typed" stacks (e.g. stack_st_X509); if not, it uses "generic" 
stacks (e.g. stack_st).

Make sure both libraries are built against the same OpenSSL installation.

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%