Did you happen to have both libcurl-gnutls and libcurl-openssl installed, and maybe configure found the wrong one?
On 9/5/22 18:56, madmurphy wrote: > Mmm I just checked better, and the |configure| script now says: > > ... > HTTP Client: curl-openssl > ... > > That is not a good sign, right? > > > On Mon, Sep 5, 2022 at 5:47 PM madmurphy <madmurphy...@gmail.com > <mailto:madmurphy...@gmail.com>> wrote: > > Indeed, there is a dedicated package on Arch, |libcurl-gnutls| > <https://archlinux.org/packages/core/x86_64/libcurl-gnutls/>. I just > checked, and it seems that GNUnet works fine with it. Package > updated > > <https://aur.archlinux.org/cgit/aur.git/commit/?h=gnunet&id=3693252e6dcdf53bfa428b4c078729c08f68ecde>. > > --madmurphy > > > On Mon, Sep 5, 2022 at 4:25 PM Christian Grothoff > <groth...@gnunet.org <mailto:groth...@gnunet.org>> wrote: > > If Arch has a curl linked against GnuTLS, then yes. -Christian > > On 9/5/22 17:11, madmurphy wrote: > > On Arch GNUnet still depends on GNUrl, but as far as I > understood now > > cURL is preferred. Would I do the right thing if updated the Arch > > package accordingly and dropped the GNUrl dependency for good? > > > > --madmurphy >
