[
https://issues.apache.org/jira/browse/MESOS-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421655#comment-15421655
]
Matthias Bach commented on MESOS-6012:
--------------------------------------
Turns out it must have been some kind of issue with package management. The
link was there in our _self-built_ deb. But, for some reason, on the system
where I had upgraded from the 0.28.2 to the 1.0.0 package I was left with an
empty {{/usr/include/slave}} directory instead of a symlink. {{apt-get purge
libmesos-dev}} and a reinstallation of the 1.0.0 package solved the issue.
Sorry about the noise and thanks for pointing out that there should be a
symlink, which allowed me to track down the issue on our side.
> Cannot compile resource estimator modules against installed Mesos headers
> -------------------------------------------------------------------------
>
> Key: MESOS-6012
> URL: https://issues.apache.org/jira/browse/MESOS-6012
> Project: Mesos
> Issue Type: Bug
> Components: modules
> Affects Versions: 1.0.0
> Reporter: Matthias Bach
> Priority: Blocker
> Labels: mesosphere
>
> As of version 1.0.0 it is no longer possible to compile custom resource
> estimator modules against the installed Mesos headers. The error message that
> is occurs on attempt is:
> {{/usr/include/mesos/module/resource_estimator.hpp:23:46: fatal error:
> mesos/slave/resource_estimator.hpp: No such file or directory}}.
> The root cause for this seems to be that on installation headers get moved
> from {{mesos/slave}} to {{mesos/agent}}. Thus, the header path in
> {{mesos/module/resource_estimator.hpp}} will resolve correctly during the
> Mesos build, but not when compiling code against the installed headers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
