But that would also mean the build you are doing is Fromm master branch which is where the 2.2 work is being done. You want to build from the Cyrus-SASL-2.1 branch.
—Quanah > On Jul 29, 2023, at 5:40 AM, Quanah Gibson-Mount <[email protected]> wrote: > > > > --On Saturday, July 29, 2023 2:04 PM +0200 Julien ÉLIE > <[email protected]> wrote: > >> Hi Quanah, >> >>> The cyrus-sasl-2.1 branch is ready for testing for the proposed 2.1.29 >>> Cyrus SASL release. For those who know how to build from source, it >>> would be great if you can test and verify things work as expected. If >>> you have a kerberos based environment that makes use of SASL/GSSAPI for >>> a variety of purposes, please note that in any feedback. Please see >>> the "README.release" file on how to generate configure and other >>> requirements to build successfully (as well as a variety of build >>> options for testing). >> >> I'm facing an issue when configuring without OPAQUE: >> >> checking for opaque_CreateCredentialRequest in -llibopaque... no >> checking for crypto_core_ristretto255_scalar_invert in -lsodium... no >> checking for crypto_kdf_hkdf_sha512_expand in -lsodium... no >> configure: WARNING: neither libopaque nor libsodium found -- OPAQUE will >> be disabled >> checking OPAQUE... disabled >> [...] >> configure: error: conditional "OPAQUE_INTERNAL" was never defined. >> Usually this means the macro was only invoked conditionally. >> zsh: exit 1 >> >> >> Could it be fixed? > > There's a PR for it waiting on review. > > --Quanah > > ------------------------------------------ Cyrus: SASL Permalink: https://cyrus.topicbox.com/groups/sasl/T204776f7816270a8-M1b7d17a95bdc81fc6b8c98a8 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
