[jira] [Commented] (MESOS-10241) checking SASL CRAM-MD5 support... configure: error: no

["Ryan Carsten Schmidt (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748912#comment-17748912 ] 

Ryan Carsten Schmidt commented on MESOS-10241:
----------------------------------------------

I just realized this was already reported to you in bug MESOS-9752 four years ago but nobody has commented on it yet. Perhaps it can be addressed now.

> checking SASL CRAM-MD5 support... configure: error: no
> ------------------------------------------------------
>
>                 Key: MESOS-10241
>                 URL: https://issues.apache.org/jira/browse/MESOS-10241
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.8.0, 1.11.0
>         Environment: macOS 12.6.7
> Xcode 13.2.1
> Apple clang version 13.0.0 (clang-1300.0.29.30)
> Cyrus SASL 2.1.28
>            Reporter: Ryan Carsten Schmidt
>            Priority: Major
>         Attachments: mesos-crammd5-quoting.patch, mesos-crammd5-test.patch
>
>
> mesos fails to configure:
> {{checking SASL CRAM-MD5 support... configure: error: no}}
> {{-------------------------------------------------------------------}}
> {{We need CRAM-MD5 support for SASL authentication.}}
> {{-------------------------------------------------------------------}}
> The configure script is checking if a test program outputs the word "found", but on my system, the program outputs "foundfound" so the test fails. The simplest fix would be instead to check whether the test program outputs anything at all, per the attached "test" patch.
> Also, the configure check has incorrect syntax which was [introduced here|https://github.com/apache/mesos/commit/c7d1e8055ea7c0cc6c01f2d7fca95a02b890d76b]: the entire test program's code is not enclosed within square brackets. This does not appear to cause a problem in autoconf 2.71 but it's probably best to fix it before some future version of autoconf decides it is a problem, per the attached "quoting" patch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)