I checked the log and the test runs correctly.
The condition
CURLSSLSET_OK != curl_global_sslset(CURLSSLBACKEND_GNUTLS, NULL, &avail))
is evaluated against "-lcurl" and it is false.
Hence the library linked against (-lcurl) does not support GnuTLS.
The detection works.
Are you sure that your libc
I tried again, just to be sure. Still get
...
HTTP Client:curl (OpenSSL)
...
My config.log attached.
--madmurphy
On Wed, Sep 7, 2022 at 8:17 PM Martin Schanzenbach
wrote:
> I am quite sure it works now as expected so you would need to provide me
> with the config.log to de
I am quite sure it works now as expected so you would need to provide me
with the config.log to debug.
Maybe your link now points to the "Normal" curl because of the testing?
Excerpts from madmurphy's message of 2022-09-07 18:55:19 +0100:
> I now commited a programmatic check for GnuTLS. Try it ou
I now commited a programmatic check for GnuTLS. Try it out. It should not
require your fix.
Mmm without my trick the configure script still prints
...
HTTP Client:curl (OpenSSL)
...
--madmurphy
On Wed, Sep 7, 2022 at 3:44 PM Schanzenbach, Martin
wrote:
>
>
> > On 7. Sep 20
Imagine that a "GET /download" downloads 1GB of data.
If your code looks like this (not the actual API but for demonstration
purposes):
data = wget_get("/download")
// Wait until download completes
Then you have a blocking API.
Instead you can have a non-blocking API that allows you to "select"
> On 7. Sep 2022, at 14:59, madmurphy wrote:
>
> Hi Martin,
>
> That means, if you can find out how the packages linked against
> libcurl-compat or libcurl-gnutls are built from source, you can do the same
> with the gnunet package.
> The packages in the official repositories that explicitly
I never used the curl API, so I don't know what the multi interface is, but
if I remember correctly wget2 introduced non-blocking sockets. That's all I
know. I did not find a lot of info on Google, except maybe for this email
on gnutls mailing list:
https://lists.gnutls.org/pipermail/gnutls-devel/2
We need a non-blocking API such as curl_multi.
Last time I checked, libwget2 does not have that.
BR
> On 7. Sep 2022, at 15:46, madmurphy wrote:
>
> I don't know all the reasons behind using curl and all GNUnet's requirements,
> but have you guys thought about switching to wget2? It is a GNU p
I don't know all the reasons behind using curl and all GNUnet's
requirements, but have you guys thought about switching to wget2? It is a
GNU package and has a nice library (libwget). It supports GNU TLS natively,
it is supposed to download faster than curl, and if a minor feature is
missing it mig
Hi Martin,
That means, if you can find out how the packages linked against
libcurl-compat or libcurl-gnutls are built from source, you can do the same
with the gnunet package.
The packages in the official repositories that explicitly require
libcurl-gnutls (and not simply libcurl) are spotify-lau
10 matches
Mail list logo
