Re: [cctbxbb] Boost Python 1.56

+1 On 10 Feb 2016, at 16:48, Richard Gildea mailto:[email protected]> wrote: 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 mailto:[email protected]> wrote: Hi Nick, Billy and I will work on this today, -Aaron On Wed, Feb 10, 2016 at 6:40 AM, Marcin Wojdyr mailto:[email protected]> 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 mailto:[email protected]> 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-5713tel:%28510%29%20486-5713

On Wed, Feb 10, 2016 at 2:41 PM, Luc Bourhis mailto:[email protected]> 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 [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb

_______________________________________________ cctbxbb mailing list [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb

_______________________________________________ cctbxbb mailing list [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb _______________________________________________ cctbxbb mailing list [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb _______________________________________________ cctbxbb mailing list [email protected]mailto:[email protected] http://phenix-online.org/mailman/listinfo/cctbxbb -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom