Apologies for not making myself clear. I agree that libcurl4-nss-dev
has been listed earlier as a required dependency. In fact, we did have
it listed in our build scripts as well. What's new in 0.23 is that
there is now a hard runtime dependency in MesosExecutorDriver that we
have not experienced in previous releases. Is this the expected path
forward? Any chance it could be suppressed via a /configure flag if we
don't expect to use openssl functions in our python executor?

On Sat, Aug 15, 2015 at 2:04 AM, Tomas Barton <[email protected]> wrote:
> Hi,
>
> libmesos.so will be dependent on the libcurl-dev library that is present on
> the machine where you've built the package.
>
> So, in case of Debian, libmesos will be dependent on one of these packages:
>
>   libcurl4-nss-dev,libcurl4-gnutls-dev, libcurl4-openssl-dev
>
> It's not a new dependency, same applies to all 0.2x releases.
>
> Tomas
>
> On 15 August 2015 at 04:17, haosdent <[email protected]> wrote:
>>
>> Hello, libcurl-nss is provider openssl functions. In
>> http://mesos.apache.org/gettingstarted/, you could see
>>
>> ```
>> # Install other Mesos dependencies.
>> $ sudo apt-get -y install build-essential python-dev python-boto
>> libcurl4-nss-dev libsasl2-dev maven libapr1-dev libsvn-dev
>> ```
>>
>> On Sat, Aug 15, 2015 at 2:08 AM, Maxim Khutornenko <[email protected]>
>> wrote:
>>>
>>> Hi,
>>>
>>> There seems to be a new runtime dependency in 0.23 MesosExecutorDriver
>>> that we did not have before. Importing MesosExecutorDriver from
>>> mesos.native against a python egg built with all default flags fails
>>> with the following error:
>>>
>>> ImportError: libcurl-nss.so.4: cannot open shared object file: No such
>>> file or directory
>>>
>>> Installing libcurl4-nss-dev on Ubuntu fixes the problem but we could
>>> not find any notes in the release that would highlight this new
>>> runtime requirement. Were there any announcements we missed? Are there
>>> any make flags we could use to suppress this dependency when building
>>> an egg?
>>>
>>> Thanks,
>>> Maxim
>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>
>

Reply via email to