Skip to content
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

Shiboken segfault when building rviz on Arch Linux #728

Closed
bchretien opened this issue Feb 25, 2014 · 4 comments
Closed

Shiboken segfault when building rviz on Arch Linux #728

bchretien opened this issue Feb 25, 2014 · 4 comments

Comments

@bchretien
Copy link
Contributor

Hi!

This is an issue similar to ros-visualization/qt_gui_core#35

Shiboken 1.2.1 was temporarily disabled for qt_gui_cpp (cf. ros-visualization/qt_gui_core#38), but this issue also happens when building rviz with shiboken support. I missed that one when packaging for Arch since I removed pyside from my system a while ago, but some users contacted me today about this issue. I guess a similar patch could be applied to src/python_bindings/shiboken/CMakeLists.txt.

Thanks!

@wjwwood
Copy link
Member

wjwwood commented Feb 25, 2014

Can you open a pull request to that effect and test it (or get the people reporting the issue to test it)? I don't have an Arch machine handy.

@wjwwood wjwwood added this to the untargeted milestone Feb 25, 2014
@bchretien
Copy link
Contributor Author

I made a patch, but I may have found a new linker error in hydro-devel as well. I'll get back to you asap.

@wjwwood
Copy link
Member

wjwwood commented Feb 25, 2014

Thanks.

@wjwwood wjwwood modified the milestones: 1.10.12 - Hydro, untargeted Feb 25, 2014
@bchretien
Copy link
Contributor Author

Nevermind, linker error was just a hiccup while linking to Ogre 1.8 (we're still using that on Arch, I think some ROS packages are still not ready for a move to Ogre 1.9). PR incoming!

wjwwood added a commit that referenced this issue Feb 26, 2014
Disable shiboken when version is detected which would segfault (fix #728)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants