[
https://issues.apache.org/jira/browse/MESOS-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175767#comment-14175767
]
Kevin Sweeney commented on MESOS-1010:
--------------------------------------
This appears to be affecting aurora as well - our end-to-end test (which uses
vagrant with an ubuntu 14.04) needs this egg, and I can't seem to build one
that doesn't result in
{noformat}
ImportError:
/root/.pex/install/mesos.native-0.20.0-py2.7-linux-x86_64.egg.5d07cc122d40d60ad6f08c27afe95a929161ffa0/mesos.native-0.20.0-py2.7-linux-x86_64.egg/mesos/native/_mesos.so:
undefined symbol: _ZN6google14FlagRegistererC1EPKcS2_S2_S2_PvS3_
{noformat}
> Python extension build is broken if gflags-dev is installed
> -----------------------------------------------------------
>
> Key: MESOS-1010
> URL: https://issues.apache.org/jira/browse/MESOS-1010
> Project: Mesos
> Issue Type: Bug
> Components: build, python api
> Environment: Fedora 20, amd64. GCC: 4.8.2.
> Reporter: Nikita Vetoshkin
>
> In my environment mesos build from master results in broken python api module
> {{_mesos.so}}:
> {noformat}
> nekto0n@ya-darkstar ~/workspace/mesos/src/python $
> PYTHONPATH=build/lib.linux-x86_64-2.7/ python -c "import _mesos"
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> ImportError:
> /home/nekto0n/workspace/mesos/src/python/build/lib.linux-x86_64-2.7/_mesos.so:
> undefined symbol: _ZN6google14FlagRegistererC1EPKcS2_S2_S2_PvS3_
> {noformat}
> Unmangled version of symbol looks like this:
> {noformat}
> google::FlagRegisterer::FlagRegisterer(char const*, char const*, char const*,
> char const*, void*, void*)
> {noformat}
> During {{./configure}} step {{glog}} finds {{gflags}} development files and
> starts using them, thus *implicitly* adding dependency on {{libgflags.so}}.
> This breaks Python extensions module and perhaps can break other mesos
> subsystems when moved to hosts without {{gflags}} installed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
