MantisBT - CMake
View Issue Details
0011769CMakeCMakepublic2011-01-27 07:342016-06-10 14:31
Tomáš Chvátal 
Kitware Robot 
normalmajoralways
closedmoved 
CMake 2.8.3 
 
0011769: cmake run commands in Finders with user locale environment set
Cmake executes all commands within the FindFoo.cmake with all evironment set up by the user thus translations are able to bork up stuff quite easily.

Currently known version of this issue can be observed with bison and language set to ES.
LC_ALL="C" and LC_ALL="sv_SE.UTF-8" you got "bison (GNU Bison) 2.4.3",
while with spanish you got: "bison (GNU bison) 2.4.2"

Thanks to the change in that Gnu *b*ison the regexp in finder no longer finds its stuff and explodes (this issue was found by running FindModulesExecuteAll test :P).

Since this issue might not be only this case it might be safest to run all cmake commands with environment reseted to C with the LC_ALL variable instead of just setting the LOCALE=C.
No tags attached.
Issue History
2011-01-27 07:34Tomáš ChvátalNew Issue
2011-01-27 15:14Alex NeundorfNote Added: 0025111
2011-01-27 15:36Tomáš ChvátalNote Added: 0025112
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030224
2016-06-10 14:28Kitware RobotNote Added: 0041789
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
(0025111)
Alex Neundorf   
2011-01-27 15:14   
At least for FindBISON.cmake this has been fixed in 2.8.4.

This leaves the question whether Find-modules in general should reset this env.variables.

Alex
(0025112)
Tomáš Chvátal   
2011-01-27 15:36   
Well i would not trust any environment, cause translators can make typos. I would be all hands for reseting all env to C as i wrote above :)

The bison issue is minor, but things like this can occur from time to time and we should rather take some steps to prevent it from happening :)
(0030224)
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.
(0041789)
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.