-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'make posix_sitl_default gazebo' exiting with Error 1 #8938
'make posix_sitl_default gazebo' exiting with Error 1 #8938
Comments
@varunvp Can you test with that branch: https://github.com/PX4/sitl_gazebo/tree/pr-fix_isinf for the
|
I'll try it right away. |
Thanks Chris, it works now!
|
esiee@esiee-HP-xw4400-Workstation:~/src/Firmware$ make posix_sitl_default gazeboninja: Entering directory `/home/esiee/src/Firmware/build/posix_sitl_default' CMake Warning at /usr/share/cmake-3.5/Modules/FindBoost.cmake:725 (message): CMake Warning at /usr/share/cmake-3.5/Modules/FindBoost.cmake:725 (message): CMake Error at /usr/share/cmake-3.5/Modules/FindBoost.cmake:1677 (message): Unable to find the Boost header files. Please set BOOST_ROOT to the root CMake Error at CMakeLists.txt:29 (find_package): Could not find a package configuration file provided by "gazebo" with any
Add the installation prefix of "gazebo" to CMAKE_PREFIX_PATH or set -- Configuring incomplete, errors occurred! I am also having the same problem but I can't find the solution of above, could some one please help me to find a solution? thanks! |
@QuimItarte This issue was closed. Suggest you repost a new issue with information about your setup. - what OS you are running on, what installation instructions you followed (generally for Linux I use the scripts here. |
Hello,
The title says it all. I'm running Gazebo 7.11 and ROS Indigo on 14.04. This is what I get when I run make posix_sitl_default gazebo
It always exits at 'Performing configure step for 'sitl_gazebo'. I have added the c++ path to PATH.
I searched the net for similar errors, but I didn't encounter any exiting with Error 1.
The text was updated successfully, but these errors were encountered: