[cmake-developers] Hacking kwsys processor detection

[Rolf Eike Beer]

I was a bit bored and decided to hack a bit on a bug I filed long ago 
(http://cmake.org/Bug/view.php?id=10895). I have attached the first 3 patches I 
came up with. I think #1 should just be applied without any further checks ;) 
The other 2 are currently only compile tested. I think they should do no harm, 
but the main intent of this mail is: how do I easily check that this code 
works? Is there a easy point where I can grab out all the information that 
this class has about the system without adding debug statements everywhere?

Also the 80-character limit is enforced for kwsys commits, but as you can see 
the file violates this itself pretty often.

Eike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-kwsys-fix-typos.patch
Type: text/x-patch
Size: 3164 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120908/df55c5a7/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-kwsys-sum-up-all-caches-found-in-proc-cpuinfo.patch
Type: text/x-patch
Size: 1898 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120908/df55c5a7/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-kwsys-PA-RISC-chips-are-from-HP.patch
Type: text/x-patch
Size: 3629 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120908/df55c5a7/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120908/df55c5a7/attachment.sig>