[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gsasl 2.1.1
From: |
Simon Josefsson |
Subject: |
Re: gsasl 2.1.1 |
Date: |
Fri, 02 Sep 2022 20:07:30 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
"Jose E. Marchesi" <jemarch@gnu.org> writes:
> Build failed with this error:
>
> ../../src/gsasl.c: In function 'main':
> ../../src/gsasl.c:870:48: error: 'GNUTLS_TLS1_3' undeclared (first use in
> this function)
> if (gnutls_protocol_get_version (session) < GNUTLS_TLS1_3)
> ^~~~~~~~~~~~~
> ../../src/gsasl.c:870:48: note: each undeclared identifier is reported only
> once for each function it appears in
>
> Sounds like something to be checked at configure time? Probably related
> configure activity:
>
> checking for libgnutls... yes
> checking how to link with libgnutls... -lgnutls
> checking if STARTTLS support via GnuTLS should be built... yes
> checking for gnutls_session_channel_binding... yes
> checking whether GNUTLS_CB_TLS_EXPORTER is declared... no
Hi Jose. Many thanks for testing, it was easy to reprduce on Debian 10
and should be fixed here:
https://git.savannah.gnu.org/cgit/gsasl.git/commit/?id=c233d6c2cfadf0ff319540a40110c10a7580b8c1
One reason this took so long to fix was that after enabling GnuTLS
builds for CI/CD (which we apparently had forgotten to do before) and
writing the gsasl-mailutils-tls.sh self-check to actually do something
useful, I ran into a bug in very recent gcc that took a while to track
down:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106427
To work around it, you may invoke ./configure with
gl_cv_warn_c__Wuse_after_free_3=no but I'm not sure what more we can do
here...
/Simon
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: gsasl 2.1.1,
Simon Josefsson <=