Re: [Rdkit-devel] 2019_03_1b1: lots of undefined references to libboost_iostreams functions

[Greg L. <gre...@gm...>]

Hi Gabriele,

I haven't tried a boost 1.70 build yet, so I can't confirm that it works.
Could you please try 1.69 and see if that helps?
If not, please send the exact cmake command you used and what the output
was.

Thanks,
-greg


On Sat, Apr 6, 2019 at 3:53 PM <bal...@un...> wrote:

> hello,
>
> there seems to be a glitch in the 2019_03_1b1 build process, where a lot
> of link steps fail for me with undefined references to
> libboost_iostreams functions. Eg:
>
>     ----8<----
>     /usr/bin/ld: lib/libRDKitmaeparser.so.1.2019.03.1b1: undefined
> reference to `boost::iostreams::zlib::deflated'
>     /usr/bin/ld: lib/libRDKitmaeparser.so.1.2019.03.1b1: undefined
> reference to `boost::iostreams::detail::zlib_base::before(char const*&,
> char const*, char*&, char*)'
>
>     [...]
>
>     /usr/bin/ld: lib/libRDKitmaeparser.so.1.2019.03.1b1: undefined
> reference to `boost::iostreams::zlib::default_compression'
>     collect2: error: ld returned 1 exit status
>     ---->8----
>
> I can make my build complete successfully only with:
>     export LDFLAGS="-lboost_iostreams"
> Is this to be expected or is there a problem with the build process?
> (all previous releases didn't need that)
>
> I can add that ./External/CoordGen/CMakeLists.txt
> ./Code/GraphMol/FileParsers/CMakeLists.txt and
> ./Code/RDStreams/CMakeLists.txt do actually contain a:
>    set (link_iostreams ${Boost_LIBRARIES})
> definition, but apparently link_iostreams is eventually empty (but I
> might not have followed correctly the logic of the cmake files)
>
> Building on linux vs boost-1_70_0_rc1
>
> thanks a lot
> ciao
> gabriele
>
>
> _______________________________________________
> Rdkit-devel mailing list
> Rdk...@li...
> https://lists.sourceforge.net/lists/listinfo/rdkit-devel
>