On 09/22/2012 12:05 PM, Bertrand Marc wrote: > (CCing upstream to try and solve the issue) > > Hello Christopher, Hello Christian, > > Le 26/08/2012 21:52, Christopher Schramm a écrit : >>> Starting GNUnet: libgcrypt has not the expected version (version 1.5.0 >>> is required). > > Ok, I understand the issue: GNUnet checks the version of libgcrypt in > src/util/crypto_random.c and returns an error if it is not the version > GNUnet was compiled against. > > Christian, is this check mandatory ? Debian uses symbols files in order > to generate more accurate library dependencies for applications, based > on the symbols from the library that are actually used by the > application. So checking the library version is done at install time and > we should not bother at execution time. > > Cheers, > Bertrand
Dear Bertrand, I understand your concern. There is no GNUnet-specific reason why we need the header-version at compile-time to match exactly the runtime-version of libgcrypt; however, libgcrypt requires calling 'gcry_check_version' and then internally performs some kind of compatibility check. GNUnet follows *exactly* (AFAIK) the recommendations of the libgcrypt manual: http://www.gnupg.org/documentation/manuals/gcrypt/Initializing-the-library.html#Initializing-the-library So if the gcry_check_version test is somehow too strict, you should take it up with Werner Koch (libgcrypt/gnupg maintainer). If Werner recommends that we change this test in any way, I'll of course be happy to do so. Werner, the exact code GNUnet uses should be at: https://gnunet.org/doxygen/df/d11/crypto__random_8c_source.html#l00338 Happy hacking! Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
