[gnutls-dev] opencdk-0.6.1 vs. gnutls-1.6.3

Simon Josefsson simon at josefsson.org
Wed Jun 6 01:13:13 CEST 2007


Gnutls 1.6.x doesn't work with OpenCDK 0.6.x, you'll need OpenCDK  
0.5.x, or --enable-included-opencdk.  I am sorry for the problems,  
but the OpenCDK maintainer wanted to fix some things and that lead to  
API/ABI breaks.

/Simon

On 5 jun 2007, at 22.56, Thomas Klausner wrote:

> Hi!
>
> The latest release of opencdk, 0.6.1, breaks the compilation of the
> latest non-development release of gnutls, 1.6.3:
> gnutls_openpgp.c: In function 'openpgp_pk_to_gnutls_cert':
> gnutls_openpgp.c:294: warning: passing argument 4 of 'cdk_pk_get_mpi'
> makes integer from pointer without a cast
> gnutls_openpgp.c:294: error: too few arguments to function
> 'cdk_pk_get_mpi'
> gnutls_openpgp.c: In function '_gnutls_openpgp_raw_privkey_to_gkey':
> gnutls_openpgp.c:337: warning: assignment makes pointer from integer
> without a cast
> gnutls_openpgp.c:363: warning: passing argument 4 of 'cdk_pk_get_mpi'
> makes integer from pointer without a cast
> gnutls_openpgp.c:363: error: too few arguments to function
> 'cdk_pk_get_mpi'
> gnutls_openpgp.c:376: warning: passing argument 4 of 'cdk_sk_get_mpi'
> makes integer from pointer without a cast
> gnutls_openpgp.c:376: error: too few arguments to function
> 'cdk_sk_get_mpi'
> gnutls_openpgp.c: In function  
> 'gnutls_certificate_set_openpgp_key_mem':
> gnutls_openpgp.c:583: error: too few arguments to function
> 'cdk_stream_tmp_from_mem'
> gnutls_openpgp.c:678: error: too few arguments to function
> 'cdk_stream_tmp_from_mem'
> gnutls_openpgp.c: In function
> 'gnutls_certificate_set_openpgp_key_file':
> gnutls_openpgp.c:744: warning: passing argument 2 of
> 'read_binary_file' from incompatible pointer type
> gnutls_openpgp.c:751: warning: passing argument 2 of
> 'read_binary_file' from incompatible pointer type
> gnutls_openpgp.c: In function
> 'gnutls_certificate_set_openpgp_keyring_mem':
> gnutls_openpgp.c:944: error: too few arguments to function
> 'cdk_stream_tmp_from_mem'
>
> Is there a workaround, or is a new gnutls out very soon?
>  Thomas





More information about the Gnutls-devel mailing list