MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009825CMakeCMakepublic2009-11-02 21:452016-06-10 14:31
ReporterR Wackerbarth 
Assigned ToZach Mullen 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionFixed in Version 
Summary0009825: FreeBSD may not have procfs. Causes CPU identification, etc. to fail to be determined properly.
DescriptionSystemInformation.cxx assumes that FreeBSD has the Linux procfs in order to get /proc/cpuinfo.

This is not a part of FreeBSD, per se, but a part of the Linux compatability modules. As a result, the information may not be available in this manner.

The "Unix" way is to use sysctl, as is done on Darwin.

Unfortunately, the sysctl namespace is not uniformly available across platforms.
As a result, FreeBSD will need its own implementation of ParseSysCtl().
Steps To Reproduce
Additional InformationI'll try to write an appropriate implementation of ParseSysCtl() for FreeBSD.
TagsNo tags attached.
Relationships
related to 0010895closed  Processor detection is very x86-specific 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-11-02 21:45R WackerbarthNew Issue
2009-11-03 10:04Bill HoffmanStatusnew => assigned
2009-11-03 10:04Bill HoffmanAssigned To => Bill Hoffman
2009-11-03 10:04Bill HoffmanAssigned ToBill Hoffman => Zach Mullen
2009-11-03 10:05Bill HoffmanNote Added: 0018328
2010-01-04 14:55Zach MullenNote Added: 0019024
2010-01-04 14:57Zach MullenNote Deleted: 0019024
2011-01-18 14:37David ColeRelationship addedrelated to 0010895
2016-06-10 14:27Kitware RobotNote Added: 0041608
2016-06-10 14:27Kitware RobotStatusassigned => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0018328)
Bill Hoffman   
2009-11-03 10:05   
A patch would be welcome. :)
(0041608)
Kitware Robot   
2016-06-10 14:27   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.