[
https://issues.apache.org/jira/browse/THRIFT-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259031#comment-14259031
]
Jens Geyer commented on THRIFT-1771:
------------------------------------
{quote}
I don't know if it currently configurable in Thrift to change from static ->
dynamic, but please don't force dynamic dependencies.
{quote}
I think it's not so much about forcing. If any, then it is the static libs that
are enforced because the Makefile linkes against e.g.
libboost_unit_test_framework.a instead of libboost_unit_test_framework. It
seems that some maintainers are going towards preferring the .so libraries.
Just one example from some more I found: "[Static linking is generally
discouraged ...|https://forums.gentoo.org/viewtopic-t-730625-start-0.html]";.
Sure, I can always build the libs from source, but ...
> "make check" fails on x64 for libboost_unit_test_framework.a
> ------------------------------------------------------------
>
> Key: THRIFT-1771
> URL: https://issues.apache.org/jira/browse/THRIFT-1771
> Project: Thrift
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.9
> Environment: Fedora 17 x86 with boost-devel and boost-static
> installed via yum
> Reporter: Chris Stylianou
> Assignee: Roger Meier
> Priority: Minor
> Labels: boost, test, thrift
> Fix For: 0.9.2
>
> Attachments:
> 0001-THRIFT-1771-make-check-fails-on-x64-for-libboost_uni.patch
>
>
> When trying to build thrift, running the "make check" testsuite fails due to
> the make file generated by ./configure pointing to dependency
> libboost_unit_test_framework.a at "$(BOOST_ROOT_PATH)/lib/". However on an
> x64 systems, this is actually located in "$(BOOST_ROOT_PATH)/lib64/".
> Also, is it possible to use the dynamic libraries instead of static?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
