Boost logo

Boost Interest :

Subject: Re: [Boost-cmake] Labels for known failures
From: Michael Jackson (mike.jackson_at_[hidden])
Date: 2009-05-19 09:30:04


I am having some trouble wrapping my head around what exactly is meant


Is that logical per core, per CPU or what? Right now I calculate the
value based on the number of logical and physical. So for my Xeon with
HyperThreading I get a value of 8. Does that seem correct?

For the other machines all the other items seem to be reporting ok.
And looking at the sysctl reports that Troy sent all the values that
are getting used seem to be the appropriate ones.

I am trying to work through the Memory calculations at the moment and
get the VM stats at the same time.

Also, there is another entry:
Is64Bits: 0

Which can mean multiple things. The way it is written now this simply
tells if CMake was compiled in 32Bit or 64 Bit mode. Was that supposed
to mean is the CPU 64 Bit capable?


Mike Jackson       
On May 19, 2009, at 7:27 AM, David Cole wrote:
> On Mon, May 18, 2009 at 3:50 PM, Brad King <brad.king_at_[hidden]>  
> wrote:
> Michael Jackson wrote:
>  thanks for the heads up about vxl. I took those 2 scripts and  
> adapted them for boost. I have since been able to submit an  
> experimental Dashboard to < 
> >. Look for ferb_at_[hidden] - the one that actually ran all the  
> tests.
> Nice.
> Also, if you click on the "site" you get some stats about the  
> machine that built boost.. All of which is either wrong or not  
> filled in. Are there some configuration options for this that need  
> to be set or is the parsing code for CTest not grepping OS X  
> machines correctly?
> IIRC it's parsed by code in the "Source/kwsys/SystemInformation.cxx"
> source in CMake:
> I looked at this issue briefly a couple months ago, but was too busy  
> to make a ctest fix at the time. The problem with SystemInformation  
> on Mac OSX is that the command lines used to gather the information  
> do not use a full path to execute the programs. We should do a  
> FIND_PROGRAM equivalent and use the full path to the programs  
> because the environment of running from a crontab entry does not  
> have the same PATH setup that a typical Mac terminal shell does...
> I just opened a cmake/ctest bug and assigned it to myself so it does  
> not get lost in the shuffle...
> HTH,
> David
> _______________________________________________
> Boost-cmake mailing list
> Boost-cmake_at_[hidden]

Boost-cmake list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at