You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:28:14 UTC
[jira] [Issue Comment Deleted] (MESOS-9659) libmesos from cmake
builds is underlinked.
[ https://issues.apache.org/jira/browse/MESOS-9659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated MESOS-9659:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> libmesos from cmake builds is underlinked.
> --------------------------------------------
>
> Key: MESOS-9659
> URL: https://issues.apache.org/jira/browse/MESOS-9659
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 1.8.0
> Reporter: Till Toenshoff
> Priority: Major
>
> While playing with module build environments using cmake, I noticed that libmesos differs a lot when comparing autotools and cmake artifacts. The libmesos cmake artifact is missing the protobuf as well as the libprocess symbols. We are expecting libmesos to include those symbols.
> h2. autotools build
> {noformat}$ nm libmesos.dylib |c++filt |grep "~TaskStatus()"
> 0000000003cc75a0 T mesos::TaskStatus::~TaskStatus()
> 0000000003cc7580 T mesos::TaskStatus::~TaskStatus()
> 0000000003cc7190 T mesos::TaskStatus::~TaskStatus()
> 0000000004179b90 T mesos::v1::TaskStatus::~TaskStatus()
> 0000000004179b70 T mesos::v1::TaskStatus::~TaskStatus()
> 00000000041798b0 T mesos::v1::TaskStatus::~TaskStatus(){noformat}
> {noformat}$ nm libmesos.dylib |c++filt |grep "process::Time::create(double)"
> 0000000004ced660 T process::Time::create(double){noformat}
> h2. cmake build
> {noformat}$ nm libmesos.dylib |c++filt |grep "~TaskStatus()"
> U mesos::TaskStatus::~TaskStatus()
> U mesos::v1::TaskStatus::~TaskStatus(){noformat}
> {noformat}$ nm libmesos.dylib |c++filt |grep "process::Time::create(double)"
> U process::Time::create(double){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)