gnutls-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Git repository --- build errors


From: Nikos Mavrogiannopoulos
Subject: Re: Git repository --- build errors
Date: Wed, 02 Dec 2009 22:55:39 +0200
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

address@hidden wrote:
> Hello,
> 
> I managed to build the package from the git repository at Savannah, but I
> had to fix several errors:
> 
> 1.
> cryptodev.c:46: error: 'EALG_MAX_BLOCK_LEN' undeclared here (not in a
> function)

Hi,
 I'm curious which system is that? Could you send me your cryptodev.h?
(now by default cryptodev shouldn't be used unless specified in configure)

> 3.
> 
> /home/lfinsto/gnutls/doc//gnutls.texi:4077: Cross reference to nonexistent
> node `gnutls_crypto_digest_register2' (perhaps incorrect sectioning?).
> /home/lfinsto/gnutls/doc//gnutls.texi:4053: Cross reference to nonexistent
> node `gnutls_crypto_single_mac_register2' (perhaps incorrect sectioning?).
> 
> Solved by commenting-out these lines in `gnutls.texi'.

This should be fixed by now.


> I hope this report is useful.

Indeed!

> There's another thing which may or may not be an issue from the point of
> view of the GNUTLS developers:  I usually program in C++ and I've been
> using code from the samples in the documentation and compiling with g++. 
> Several times I've had to add explicit casts of pointers where C doesn't
> require them but C++ does.  Not wishing to interfere in something that's
> not my business, but I thought I'd mention this in case the developers
> think that compatibility with C++ would be desirable.

Do you use the C++ compatibility API or do you call the C functions
directly? Currently the idea is to have the C api, and the alternative
C++ API, to be used by C++ applications.

regards,
Nikos




reply via email to

[Prev in Thread] Current Thread [Next in Thread]