The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I just ran into the same problem (no idea why this didn't happen before). Turns out that eclipse can't parse localized gcc messages, so the auto-discovery of standard include paths from the gcc output fails. Solution:
LC_ALL=C eclipse
(Who actually wants localized error messages from gcc? The German translation usually makes them even more cryptic, IMO...)
| | 2 | No.2 Revision |
I just ran into the same problem (no idea why this didn't happen before). Turns out that eclipse can't parse localized gcc messages, so the auto-discovery of standard include paths from the gcc output fails. Solution:
LC_ALL=C eclipse
Or, if you like that better: "Window -> Preferences -> C/C++ -> Build -> Environment", add two new environment variables "LANG" and "LC_ALL" and set them both to "en_US" or "C". Also see this eclipse forum post.
(Who actually wants localized error messages from gcc? The German translation usually makes them even more cryptic, IMO...)
| | 3 | No.3 Revision |
Update: After trying to reproduce this on a fresh work space, it turned out that I was wrong, LC_ALL has nothing to do with it. @stomic's answer is correct. I had to follow these steps (Eclipse Juno, ROS Groovy):
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.