MantisBT - CMake
View Issue Details
0012066CMakeCMakepublic2011-04-11 02:032016-06-10 14:31
alexey kutumov 
Kitware Robot 
normalminoralways
closedmoved 
sparcSunOC5.10
CMake 2.8.4 
 
0012066: wrong using kstat in CMake/CTest
Wrong parameter name passed to kstat, when using CTest under Solaris:
syste_misc

it must be: system_misc
call CTest under SunOS
Source\kwsys\SystemInformation.cxx

bool SystemInformationImplementation::QuerySolarisInfo();
No tags attached.
Issue History
2011-04-11 02:03alexey kutumovNew Issue
2011-04-11 02:59alexey kutumovNote Added: 0026162
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030252
2016-06-10 14:28Kitware RobotNote Added: 0041832
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0026162)
alexey kutumov   
2011-04-11 02:59   
Also, during performing tests, CTest prints to console:

Error kstat returned :12
Error kstat returned :12
Error kstat returned :1
Error kstat returned :12
Error kstat returned :12
Error kstat returned :12
Error kstat returned :12
Error kstat returned :1
(0030252)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041832)
Kitware Robot   
2016-06-10 14:28   
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.