Re: [Boost-bugs] [Boost C++ Libraries] #4866: Tests don't account for locally-built bzip2 library

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4866: Tests don't account for locally-built bzip2 library
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-12-12 21:54:03

#4866: Tests don't account for locally-built bzip2 library
  Reporter: dave | Owner: vladimir_prus
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: build
   Version: Boost 1.44.0 | Severity: Problem
Resolution: | Keywords:

Comment (by Leo Carreon <lcarreon@…>):


 I have encountered the same problem in Boost 1.47.0 and suspect the same
 problem is still present in Boost 1.48.0. With the help of dumpbin.exe, I
 have discovered that the import library boost_bzip2-vc100-mt-1_47.lib
 points to libbz2.dll instead of boost_bzip2-vc100-mt-1_47.dll. Currently,
 the work-around is to copy boost_bzip2-vc100-mt-1_47.dll to libbz2.dll.

 I have tried looking into the JAM files to find out why the import library
 is pointing to the wrong DLL name to no avail because I'm such a newbie
 with JAM files. I'm suspecting that the DLL and the import libraries were
 built using libbz2 as their names and then renamed to the Boost library
 naming convention thus the reason for the import library to be referring
 to the wrong DLL name.

 Does this make sense?

 The other thing that's confusing me is why the ZLIB library that is built
 together with the BZIP2 library is not exhibiting the same problem. This
 could disprove my theory about the renaming since the two libraries appear
 to be built from within the same JAM file.

 Kind regards,

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:08 UTC