On Tue, Mar 14, 2017 at 11:18 AM Tomasz Kłoczko <kloczko.tomasz@xxxxxxxxx> wrote:
On 14 March 2017 at 07:24, Dan Horák <dan@xxxxxxxx> wrote:g++: error: /usr/lib/libboost_unit_test_framework.a: No such file or
directory
the thrift buildsystem doesn't treat ppc64le as a 64-bit arch
with /usr/lib64, probably there is a hard-coded list of arches ...Despite such simple to fix bug using static libraries should be removed.
Your comment makes me wonder if there is *any* appropriate use of boost-static. If not, why is it even packaged?
I'd be happy to accept your help patching what upstream is doing to move from boost-static to boost-test (I'm not sufficiently knowledgeable about C/C++ tooling to switch on my own), but since the dependency is limited to unit testing during the build, I think it's probably fine.
I'd be happy to accept your help patching what upstream is doing to move from boost-static to boost-test (I'm not sufficiently knowledgeable about C/C++ tooling to switch on my own), but since the dependency is limited to unit testing during the build, I think it's probably fine.
kloczek_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
