<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Richard</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 10 Feb 2016, at 16:44, Aaron Brewster <<a href="mailto:asbrewster@lbl.gov" class="">asbrewster@lbl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Nick, Billy and I will work on this today,<div class=""><br class=""></div><div class="">-Aaron</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Feb 10, 2016 at 6:40 AM, Marcin Wojdyr <span dir="ltr" class=""><<a href="mailto:wojdyr@gmail.com" target="_blank" class="">wojdyr@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FWIW the latest version of Boost is 1.60.<br class="">
CCP4 6.5 was using cctbx compiled with Boost 1.56<br class="">
and CCP4 7.0 uses Boost 1.58.<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
Marcin<br class="">
</font></span><div class="HOEnZb"><div class="h5"><br class="">
On Wed, Feb 10, 2016 at 2:17 PM, Nicholas Sauter <<a href="mailto:nksauter@lbl.gov" class="">nksauter@lbl.gov</a>> wrote:<br class="">
> Nigel, Billy & Aaron,<br class="">
><br class="">
> I completely endorse this move to Boost 1.56. Can we update our build?<br class="">
><br class="">
> Nick<br class="">
><br class="">
> Nicholas K. Sauter, Ph. D.<br class="">
> Computer Staff Scientist, Molecular Biophysics and Integrated Bioimaging<br class="">
> Division<br class="">
> Lawrence Berkeley National Laboratory<br class="">
> 1 Cyclotron Rd., Bldg. 33R0345<br class="">
> Berkeley, CA 94720<br class="">
> <a href="tel:%28510%29%20486-5713" value="+15104865713" class="">(510) 486-5713</a><br class="">
><br class="">
> On Wed, Feb 10, 2016 at 2:41 PM, Luc Bourhis <<a href="mailto:luc_j_bourhis@mac.com" class="">luc_j_bourhis@mac.com</a>> wrote:<br class="">
>><br class="">
>> Hi,<br class="">
>><br class="">
>> I have improvements to the smtbx on their way to be committed which<br class="">
>> require Boost version 1.56. This is related to Boost.Threads, whose support<br class="">
>> I re-activated a few months ago on Nick’s request. I need the function<br class="">
>> boost::thread::physical_concurrency which returns the number of physical<br class="">
>> cores on the machine, as opposed to virtual cores when hyperthreading is<br class="">
>> enabled (which it is by default on any Intel machine). That function is not<br class="">
>> available in Boost 1.55 which is the version currently used in the nightly<br class="">
>> tests: it appeared in 1.56.<br class="">
>><br class="">
>> So, would it be possible to move to Boost 1.56? Otherwise, I will need to<br class="">
>> backport that function. Not too difficult but not thrilling.<br class="">
>><br class="">
>> Best wishes,<br class="">
>><br class="">
>> Luc<br class="">
>><br class="">
>><br class="">
>> _______________________________________________<br class="">
>> cctbxbb mailing list<br class="">
>> <a href="mailto:cctbxbb@phenix-online.org" class="">cctbxbb@phenix-online.org</a><br class="">
>> <a href="http://phenix-online.org/mailman/listinfo/cctbxbb" rel="noreferrer" target="_blank" class="">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br class="">
><br class="">
><br class="">
><br class="">
> _______________________________________________<br class="">
> cctbxbb mailing list<br class="">
> <a href="mailto:cctbxbb@phenix-online.org" class="">cctbxbb@phenix-online.org</a><br class="">
> <a href="http://phenix-online.org/mailman/listinfo/cctbxbb" rel="noreferrer" target="_blank" class="">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br class="">
><br class="">
<br class="">
_______________________________________________<br class="">
cctbxbb mailing list<br class="">
<a href="mailto:cctbxbb@phenix-online.org" class="">cctbxbb@phenix-online.org</a><br class="">
<a href="http://phenix-online.org/mailman/listinfo/cctbxbb" rel="noreferrer" target="_blank" class="">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br class="">
</div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">cctbxbb mailing list<br class=""><a href="mailto:cctbxbb@phenix-online.org" class="">cctbxbb@phenix-online.org</a><br class="">http://phenix-online.org/mailman/listinfo/cctbxbb<br class=""></div></blockquote></div><br class=""></div></body></html>