Gazebo fails to start on MacOS Catalina with "Symbol not found: _alcOpenDevice" #55
Comments
|
Hiya, could you please post the output of |
|
Here it is: Thanks for this guys. |
|
Another useful debug information would be to print the output of this command in a terminal in which the conda environment is activated: |
|
Here it is: Thanks, Alex. |
|
@Tobias-Fischer did you ever tried in the past the Gazebo conda-forge binary on macOS? On which macOS version? If we never tested Gazebo on macOS to be working correctly, then the explanation could be that there may be a bug in Gazebo upstream in handling the OpenAL dependency, in particular in https://github.com/osrf/gazebo/blob/b0dfa186838de0874e0084bf0e08d4f0a1d6f15c/cmake/SearchForStuff.cmake#L74 OpenAL is enabled without the possibility of disabling it, but only gazebo_common (https://github.com/osrf/gazebo/blob/67c43463c87685b7c9d485a9f8d2e6ac760815b9/gazebo/common/CMakeLists.txt#L274) and not gazebo_util are linked to it. If instead Gazebo via conda-forge on other macOS machines was tested to run, then there may be something specific going on @sonelu system, perhaps related to the OS version or something else. |
5 tasks
|
I added a regression test to understand if this is a problem of the gazebo binary in conda-forge/gazebo-feedstock#54 . |
|
@traversaro I've seen you added So this check might not be conclusive for the conda-forge build. |
gazebo is actually a rather small process that just spawns two more process, that are the one that actually link all the libraries, that are |
|
Anyhow, nothing seems strange in conda-forge/gazebo-feedstock#54 . |
|
they both work for If I run them with |
|
Cool thanks, then indeed probably there is some library that are loaded in a lazy way, let's see if we can transform it in something that we can run and quickly get an output. |
|
Can you try to run: ? |
|
|
Ok, this trick does not work then. Does the |
|
Yes, |
Tobias-Fischer
added
bug
|
@traversaro @Tobias-Fischer I have reinstalled Gazebo after you published the patch on conda-forge and now I can start it (just simple start). I'm still gettting a seg fault in the If you want you can close this issue as the original problem with Gazebo is fixed. |
|
Thanks @sonelu for checking this! Actually we are experiencing some segfault in our tests, so it could be also related to Gazebo itself. We will track some issue on gazebo-feedstock to track those problems, feel free to open new issues if you isolate your problem, thanks! |
|
Let's keep discussing in #60 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment:
MacOS Catalina 10.15.7
Conda: 4.9.2
Python: 3.8.8
Installed ros-noetic-desktop-full in it's own environment.
Installation run without any error.
When starting Gazebo there is the following runtime error:
Not sure if this is relevant for the ROS build but I also have:
Thanks,
Alex.
The text was updated successfully, but these errors were encountered: