[cctbxbb] Boost Python 1.56

Richard Gildea rgildea at gmail.com
Wed Feb 10 08:48:57 PST 2016


Hi,

Is there any good reason not to move straight to the latest release, 1.60.0, assuming that everything builds/tests pass etc with that version? If we’re putting in the effort to move to a new version it makes sense to try the latest version, rather than some intermediate.

Cheers,

Richard

> On 10 Feb 2016, at 16:44, Aaron Brewster <asbrewster at lbl.gov> wrote:
> 
> Hi Nick, Billy and I will work on this today,
> 
> -Aaron
> 
> On Wed, Feb 10, 2016 at 6:40 AM, Marcin Wojdyr <wojdyr at gmail.com <mailto:wojdyr at gmail.com>> wrote:
> FWIW the latest version of Boost is 1.60.
> CCP4 6.5 was using cctbx compiled with Boost 1.56
> and CCP4 7.0 uses Boost 1.58.
> 
> Marcin
> 
> On Wed, Feb 10, 2016 at 2:17 PM, Nicholas Sauter <nksauter at lbl.gov <mailto:nksauter at lbl.gov>> wrote:
> > Nigel, Billy & Aaron,
> >
> > I completely endorse this move to Boost 1.56.  Can we update our build?
> >
> > Nick
> >
> > Nicholas K. Sauter, Ph. D.
> > Computer Staff Scientist, Molecular Biophysics and Integrated Bioimaging
> > Division
> > Lawrence Berkeley National Laboratory
> > 1 Cyclotron Rd., Bldg. 33R0345
> > Berkeley, CA 94720
> > (510) 486-5713 <tel:%28510%29%20486-5713>
> >
> > On Wed, Feb 10, 2016 at 2:41 PM, Luc Bourhis <luc_j_bourhis at mac.com <mailto:luc_j_bourhis at mac.com>> wrote:
> >>
> >> Hi,
> >>
> >> I have improvements to the smtbx on their way to be committed which
> >> require Boost version 1.56. This is related to Boost.Threads, whose support
> >> I re-activated a few months ago on Nick’s request. I need the function
> >> boost::thread::physical_concurrency which returns the number of physical
> >> cores on the machine, as opposed to virtual cores when hyperthreading is
> >> enabled (which it is by default on any Intel machine). That function is not
> >> available in Boost 1.55 which is the version currently used in the nightly
> >> tests: it appeared in 1.56.
> >>
> >> So, would it be possible to move to Boost 1.56? Otherwise, I will need to
> >> backport that function. Not too difficult but not thrilling.
> >>
> >> Best wishes,
> >>
> >> Luc
> >>
> >>
> >> _______________________________________________
> >> cctbxbb mailing list
> >> cctbxbb at phenix-online.org <mailto:cctbxbb at phenix-online.org>
> >> http://phenix-online.org/mailman/listinfo/cctbxbb <http://phenix-online.org/mailman/listinfo/cctbxbb>
> >
> >
> >
> > _______________________________________________
> > cctbxbb mailing list
> > cctbxbb at phenix-online.org <mailto:cctbxbb at phenix-online.org>
> > http://phenix-online.org/mailman/listinfo/cctbxbb <http://phenix-online.org/mailman/listinfo/cctbxbb>
> >
> 
> _______________________________________________
> cctbxbb mailing list
> cctbxbb at phenix-online.org <mailto:cctbxbb at phenix-online.org>
> http://phenix-online.org/mailman/listinfo/cctbxbb <http://phenix-online.org/mailman/listinfo/cctbxbb>
> 
> _______________________________________________
> cctbxbb mailing list
> cctbxbb at phenix-online.org
> http://phenix-online.org/mailman/listinfo/cctbxbb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phenix-online.org/pipermail/cctbxbb/attachments/20160210/5341b0bf/attachment-0001.htm>


More information about the cctbxbb mailing list