gmane.network.gnutls.general

David Reiser | 24 Jun 04:20

problems building 2.4.0

I'm trying to build GnuTLS 2.4.0 on a Mac -- OS X 10.5.3, gcc 4.0.1,  
most dependencies supplied with fink packages.

I get:
  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/sw/share/ 
locale\" -I../lgl -I../lgl -I../includes -I../includes -I./x509 -I../ 
libextra -I../lib/openpgp/ -I/sw/include -I./opencdk -I../lib/opencdk - 
I/sw/include -I/sw/include -I/sw/include -g -O2 -Wno-pointer-sign -c  
gnutls_openpgp.c  -fno-common -DPIC -o .libs/gnutls_openpgp.o
gnutls_openpgp.c: In function 'gnutls_openpgp_get_key':
gnutls_openpgp.c:219: error: 'cdk_keydb_search_t' undeclared (first  
use in this function)
gnutls_openpgp.c:219: error: (Each undeclared identifier is reported  
only once
gnutls_openpgp.c:219: error: for each function it appears in.)
gnutls_openpgp.c:219: error: syntax error before 'st'
gnutls_openpgp.c:242: error: 'st' undeclared (first use in this  
function)
gnutls_openpgp.c:242: warning: passing argument 2 of  
'cdk_keydb_search_start' makes integer from pointer without a cast
gnutls_openpgp.c:242: error: incompatible type for argument 3 of  
'cdk_keydb_search_start'
gnutls_openpgp.c:242: error: too many arguments to function  
'cdk_keydb_search_start'
gnutls_openpgp.c:244: warning: passing argument 2 of  
'cdk_keydb_search' from incompatible pointer type
gnutls_openpgp.c:244: error: too many arguments to function  
'cdk_keydb_search'
gnutls_openpgp.c:246: warning: implicit declaration of function  
'cdk_keydb_search_release'

(Continue reading)

headers

Simon Josefsson | 24 Jun 11:03

Re: problems building 2.4.0

David Reiser <dbreiser <at> gmail.com> writes:

> I'm trying to build GnuTLS 2.4.0 on a Mac -- OS X 10.5.3, gcc 4.0.1,
> most dependencies supplied with fink packages.

This seems to be the same problem as in:

http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2912

Does the patch in that thread solve the problem for you?

Perhaps we should do a 2.4.1 with this fix, but it may be too early to
do this now.

/Simon

> I get:
>  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/sw/share/
> locale\" -I../lgl -I../lgl -I../includes -I../includes -I./x509 -I../
> libextra -I../lib/openpgp/ -I/sw/include -I./opencdk -I../lib/opencdk
> -
> I/sw/include -I/sw/include -I/sw/include -g -O2 -Wno-pointer-sign -c 
> gnutls_openpgp.c  -fno-common -DPIC -o .libs/gnutls_openpgp.o
> gnutls_openpgp.c: In function 'gnutls_openpgp_get_key':
> gnutls_openpgp.c:219: error: 'cdk_keydb_search_t' undeclared (first
> use in this function)
> gnutls_openpgp.c:219: error: (Each undeclared identifier is reported
> only once
> gnutls_openpgp.c:219: error: for each function it appears in.)
> gnutls_openpgp.c:219: error: syntax error before 'st'

(Continue reading)

headers

David Reiser | 25 Jun 17:51

Re: problems building 2.4.0


On Jun 24, 2008, at 5:03 AM, Simon Josefsson wrote:

> David Reiser <dbreiser <at> gmail.com> writes:
>
>> I'm trying to build GnuTLS 2.4.0 on a Mac -- OS X 10.5.3, gcc 4.0.1,
>> most dependencies supplied with fink packages.
>
> This seems to be the same problem as in:
>
> http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2912
>
> Does the patch in that thread solve the problem for you?
Yes (though I patched Makefile.in instead).

Thanks. My googling needs some work, I guess.

>
>
> Perhaps we should do a 2.4.1 with this fix, but it may be too early to
> do this now.

Now that I have a fix, I can package it this way, so I'm not in a  
hurry for a new version.

Is using an internal opencdk likely to continue?
>
>
> /Simon
>

(Continue reading)

headers

Simon Josefsson | 25 Jun 20:33

Re: problems building 2.4.0

David Reiser <dbreiser <at> gmail.com> writes:

>> Does the patch in that thread solve the problem for you?
> Yes (though I patched Makefile.in instead).
...
>> Perhaps we should do a 2.4.1 with this fix, but it may be too early to
>> do this now.
>
> Now that I have a fix, I can package it this way, so I'm not in a
> hurry for a new version.

Great, I'd rather wait until we have more critical things to fix before
doing another 2.4.x release.

> Is using an internal opencdk likely to continue?

Alas, yes.  We don't know how to handle an abstract crypto-layer without
bundling it with GnuTLS.

Possibly we could create another project which is the crypto provider
for all gnutls projects, and gnutls and opencdk could both use them
separately.  But it is a lot of work.

/Simon