# Libpbs does not depend on libcrypto nor libpthread

**URL:** <https://community.openpbs.org/t/libpbs-does-not-depend-on-libcrypto-nor-libpthread/601>\
**Category:** Developers\
**Created:** [July 11, 2017, 4:02am UTC](https://community.openpbs.org/t/libpbs-does-not-depend-on-libcrypto-nor-libpthread/601 "2017-07-11T04:02:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![subhasisb](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/subhasisb/32/12_2.png) [@subhasisb](https://community.openpbs.org/u/subhasisb)\
**Post date:** [July 11, 2017, 4:51am UTC](https://community.openpbs.org/t/libpbs-does-not-depend-on-libcrypto-nor-libpthread/601/2 "2017-07-11T04:51:55Z")

</div>

I think it comes from the history of libpbs being distributed as an archive library, which means only necessary code was pulled into executables from libpbs.a and some of them might have needed crypto or libpthread, but not all.

Of course, now that it is a shared library, it would be way more beneficial for [libpbs.so](http://libpbs.so) to itself record the dependencies on these two.

This topic was discussed in the PBS forums here: [Compile OpenMPI with PBSpro 14.1.10](http://community.openpbs.org/t/compile-openmpi-with-pbspro-14-1-10/159/5)  
and a bug had been logged here: [https://pbspro.atlassian.net/browse/PP-360](https://pbspro.atlassian.net/browse/PP-360)

You are very welcome to submit a fix to this bug.

Thanks

---

_[View the full topic](https://community.openpbs.org/t/libpbs-does-not-depend-on-libcrypto-nor-libpthread/601)._
