[
https://issues.apache.org/jira/browse/MESOS-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936956#comment-15936956
]
Till Toenshoff edited comment on MESOS-7286 at 3/22/17 7:20 PM:
----------------------------------------------------------------
Related: https://issues.apache.org/jira/browse/MESOS-5450
However, for the above we chose a quick (and dirty!) solution. This needs a
cleanup as proposed in the ticket comments.
was (Author: tillt):
Related: https://issues.apache.org/jira/browse/MESOS-5450
> Move CRAM with MD5 support test to check rather than configure
> --------------------------------------------------------------
>
> Key: MESOS-7286
> URL: https://issues.apache.org/jira/browse/MESOS-7286
> Project: Mesos
> Issue Type: Wish
> Components: security, test, testing, tests
> Reporter: Charles Allen
>
> https://www.mail-archive.com/[email protected]/msg04222.html
> I recently ran into an issue with cross compiling very similar to what the
> user in the above thread ran into, where the SASL2 library with MD5 support
> had to be in {{LD_LIBRARY_PATH}} in order to get {{configure}} to run.
> This ask is that the test be put as one of the tests in {{make check}} rather
> than {{configure}}.
> The difference here is assuming the target environment is all setup in {{make
> check}}, but for {{configure}} the target environment paths are passed in and
> may not be equal to what is in the environment in which {{configure}} is run.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
