Opened 5 years ago
Last modified 14 months ago
#58680 assigned defect
mesos 1.7.0 build fails: "We need CRAM-MD5 support for SASL authentication"
Reported by: | chrstphrchvz (Christopher Chavez) | Owned by: | dgilman (David Gilman) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | Cc: | dgilman (David Gilman), ryandesign (Ryan Carsten Schmidt) | |
Port: | mesos |
Description
See https://paste.macports.org/85211700968d for an example:
---> Configuring mesos … checking for sasl_done in -lsasl2... yes checking SASL CRAM-MD5 support... configure: error: no ------------------------------------------------------------------- We need CRAM-MD5 support for SASL authentication. ------------------------------------------------------------------- Command failed: cd "/opt/local/var/macports/build/_Users_travis_build_macports_macports-ports_devel_mesos/mesos/work/mesos-1.7.0" && ./configure --prefix=/opt/local --with-svn=/opt/local --with-apr=/opt/local --disable-werror --disable-python --disable-java --disable-maintainer-mode Exit code: 1 Error: Failed to configure mesos, consult /opt/local/var/macports/build/_Users_travis_build_macports_macports-ports_devel_mesos/mesos/work/mesos-1.7.0/config.log Error: Failed to configure mesos: configure failure: command execution failed DEBUG: Error code: NONE DEBUG: Backtrace: configure failure: command execution failed while executing "$procedure $targetname" Error: See /opt/local/var/macports/logs/_Users_travis_build_macports_macports-ports_devel_mesos/mesos/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port mesos failed Build of 'mesos' failed.
Change History (5)
comment:1 Changed 5 years ago by dgilman (David Gilman)
comment:2 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
There have been no comments on the upstream ticket. However this error went away during the update to 1.8.0 [8347716401/macports-ports], and the port is currently known to build on 10.6 and later as of [46f85ab877/macports-ports].
comment:3 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from dgilman@… to dgilman |
---|
We still see this problem on the build servers, e.g. https://build.macports.org/builders/ports-11_x86_64-builder/builds/8626/steps/install-port/logs/stdio
comment:4 Changed 3 years ago by dgilman (David Gilman)
Taking a shot at this again with the latest upstream mesos. Right now it's not building with latest autotools - not insurmountable, but not promising. The upstream project is all but dead and personally I'm not using this for work anymore. Is anyone opposed to deprecating the port and removing it later? I really don't see a future for the port or for mesos.
comment:5 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign added |
---|
I opened https://issues.apache.org/jira/browse/MESOS-9752 to mesos upstream over this. Something changed with the MacPorts cyrus-sasl package and it now reports duplicates of each SASL plugin, which violates some assumptions made in the ./configure script.