Hi, since the last changes on gnunet concerning gnurl/curl detection I have a strange behaviour in the context of packaging gnunet for alpine-linux.
When building gnunet-0.19.3 with gnurl-7.72.0[2] the process stops at detecting libcurl. (See also [1].) ... checking for conversation feature set to build... none checking for curl_easy_getinfo in -lcurl-gnutls... no checking for gawk... (cached) awk checking for curl-config... no checking whether libcurl is usable... no ... This used to work. Now, when building gnunet-0.19.3 with curl-7.87.0 I get no error in the configure phase which is strange, because I expected that gnunet would only compile with gnurl or curl-gnutls. ... checking for conversation feature set to build... none checking for curl_easy_getinfo in -lcurl-gnutls... no checking for gawk... (cached) awk checking for curl-config... /usr/bin/curl-config checking for the version of libcurl... 7.87.0 checking for libcurl >= version 7.34.0... yes checking whether libcurl is usable... yes checking for curl_free... yes checking for curl/curl.h... yes checking whether CURLINFO_TLS_SSL_PTR is declared... yes checking for library containing __atomic_load_8... -latomic ... Right now it would be possible to package gnunet with libcurl (OpenSSL) on alpine-linux. Do I misunderstand something here? Cheers, xrs [1] https://gitlab.alpinelinux.org/xrs/aports/-/jobs/972407#L425 [2] https://pkgs.alpinelinux.org/package/v3.17/community/x86_64/gnurl -- +---------------------------------------------------------+ | Let's encrypt mail for safer communication! | +---------------------------------------------------------+ | | | Here is my public key: | | https://keys.openpgp.org/search?q=F925E518CD0DEF8A | | | | To be sure you are talking to | | me and not some strange Internet | | actor in the middle ask me for | | this fingerprint: | | | | 5D3F 2470 7F3B C77A D1B9 | | EA9A F925 E518 CD0D EF8A | | | +---------------------------------------------------------+
