MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011803CMakeCMakeSetuppublic2011-02-05 04:462016-06-10 14:31
ReporterNeil Newell 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformGNU Linux X86/GCC 4.4.5OSLinuxOS Version2.6.32.2
Product VersionCMake 2.8.3 
Target VersionFixed in Version 
Summary0011803: Build failure: 'erase' undefined (ncurses)
DescriptionWhen building CMake on linux, linking failed due to 'erase' (ncurses) being undefined in e.g cmCursesLongMessage.cxx.
Steps To ReproduceCompile against ncurses-5.7 (GCC 4.4.5 was used but probably not a factor).
Additional InformationThe issue seems to be because 'erase' is being 'hidden' via an inline function in a header file, then #undef'd to avoid possible conflict with the STL.

However, in ncurses-5.7 the same logic appears in the ncurses.h header itself; 'erase' is #undef'sd if _cplusplus is defined; as a result it is not defined in the first place.

The problem was fixed locally by replacing the 'erase()' call in the header file Source/CursesDialog/cmCursesStandardInclude.h with its macro expansion of 'werase(stdscr)'. Possibly the same fix should be applied to 'move' (in 'curses_move') although this wasn't a problem in this specific case.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-02-05 04:46Neil NewellNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030229
2016-06-10 14:28Kitware RobotNote Added: 0041794
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
(0030229)
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.
(0041794)
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.