[MacPorts] #35490: libtorrent-rasterbar won't compile against new default boost variants

[MacPorts]

#35490: libtorrent-rasterbar won't compile against new default boost variants
---------------------------------+------------------------------------------
 Reporter:  timbargen@…          |       Owner:  devans@…            
     Type:  defect               |      Status:  new                 
 Priority:  Normal               |   Milestone:                      
Component:  ports                |     Version:  2.1.2               
 Keywords:  boost, libtorrent    |        Port:  libtorrent-rasterbar
---------------------------------+------------------------------------------
Changes (by ryandesign@…):

 * cc: adfernandes, devans (removed)
 * cc: adfernandes@… (added)
  * owner:  macports-tickets@… => devans@…


Old description:

> libtorrent-rasterbar (16.2) won't pass the configure script when building
> against the new default boost (1.50) variants "+no_single" "+no_static"
> seen here:
> https://trac.macports.org/changeset/95845/trunk/dports/devel/boost/Portfile
>
> you can force it to get past the configure script by adding
> {{{
>                 --with-boost-python=mt
> }}}
> to configure.args in the portfile, but then it fails to build.
>
> rebuilding boost with "-no_single -no_static" allows libtorrent-rasterbar
> to be built with no problems.
>
> To be honest, I really don't know which one of the new default variants
> is the culprit; I didn't really feel like rebuilding boost 2 or 3 times
> just to test. I suspect its the +no_single variant though just because I
> had to tell libtorrent-rasterbar to look for the mt (multi-threaded)
> version of the library for it to even try to compile when I was using the
> new default variants for boost.
>
> Whichever it is, either -no_single/-no_static needs to be made a
> dependency for libtorrent-rasterbar, or +no_single/+no_static needs to be
> removed from the default variants for boost.
>
> I'm on 10.7.4 with a Core2 Duo for what it's worth.

New description:

 libtorrent-rasterbar (16.2) won't pass the configure script when building
 against the new default boost (1.50) variants "+no_single" "+no_static"
 seen here: changeset:95845/trunk/dports/devel/boost/Portfile

 you can force it to get past the configure script by adding
 {{{
                 --with-boost-python=mt
 }}}
 to configure.args in the portfile, but then it fails to build.

 rebuilding boost with "-no_single -no_static" allows libtorrent-rasterbar
 to be built with no problems.

 To be honest, I really don't know which one of the new default variants is
 the culprit; I didn't really feel like rebuilding boost 2 or 3 times just
 to test. I suspect its the +no_single variant though just because I had to
 tell libtorrent-rasterbar to look for the mt (multi-threaded) version of
 the library for it to even try to compile when I was using the new default
 variants for boost.

 Whichever it is, either -no_single/-no_static needs to be made a
 dependency for libtorrent-rasterbar, or +no_single/+no_static needs to be
 removed from the default variants for boost.

 I'm on 10.7.4 with a Core2 Duo for what it's worth.

--

Comment:

 The Cc field must contain complete email addresses.

-- 
Ticket URL: <https://trac.macports.org/ticket/35490#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS