rossihwang
commented
4 years ago Same issue on Ubuntu focal/ROS2 foxy
Open rotu opened 4 years ago
rossihwang
commented
4 years ago Same issue on Ubuntu focal/ROS2 foxy
dirk-thomas
commented
4 years ago Please consider to provide a pull request to support newer clang versions.
rotu
commented
4 years ago @dirk-thomas I tried but got lost in the crazy shiboken build process. I'll give it another shot. I'm out of my depth.
rotu
commented
4 years ago AFAICT, the build process should be calling the setup_clang macro in /usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.14.0/shiboken_helpers.cmake but no idea why it's not or how it should get called. I think the answer is in some of the Python scripts, but unfortunately cmake --trace doesn't give me that. Here's a trace of the cmake.
cmake-fail-qt_gui_core.txt
flynneva
commented
4 years ago anyone solve this issue? I've been digging and I cant seem to figure out a solution
rotu
commented
4 years ago I think it works after uninstalling Shiboken and installing through pip.
sudo apt remove shiboken2 libshiboken2-dev libshiboken2-py3-5.14
pip3 install --user shiboken2though I haven't tested whether it's functional - only that it builds.
@dirk-thomas is the maintainer listed in the package manifest, so I'm sure he can comment more.
flynneva
commented
4 years ago @rotu, thanks for the tip. was able to compile it as well...but also not quite sure to test if it is functional or not. rviz2 works great so maybe it is working ok?
dirk-thomas
commented
4 years ago I think it works after uninstalling Shiboken and installing through pip.
@rotu It would be helpful to narrow down what exact change between the version of the Debian package and the used via pip caused it to work for you. With that information you could request the Ubuntu package to backport the specific fix into the Debian package.
rotu
commented
4 years ago @dirk-thomas Might be this: https://bugreports.qt.io/browse/PYSIDE-1259?jql=text%20~%20%22Unable%20to%20locate%20Clang%27s%20built-in%20include%20directory%22
I'm not planning on fixing this issue. If I were, I would switch the rosdep dependency to install via pip instead of apt.
dirk-thomas
commented
4 years ago I would switch the rosdep dependency to install via pip instead of apt.
A Debian package can not depend on a package provided by pip. So that is not possible.
rotu
commented
4 years ago I would switch the rosdep dependency to install via pip instead of apt.
A Debian package can not depend on a package provided by
pip. So that is not possible.
Oof. That's a bummer. Good luck!
ros-discourse
commented
4 years ago This issue has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/is-anyone-using-ros2-gui-tools-like-rviz-on-macos/16353/9
lingxd
commented
3 years ago Did you figure out the fix for the colcon step error? I’m running into the same, and I have no success debugging it. Any help will be much appreciated! Thank you.
dongpan90
commented
3 years ago @lingxd Are you build ROS2 using the source code?
algorithmlover2016
commented
2 years ago I run a container ubuntu 20.04 with docker under macos. It should seems like I build in environment of ubuntu, why I will call clang ?
lingxd
commented
2 years ago @lingxd Are you build ROS2 using the source code?
no, I Installing ROS 2 via Debian Packages.
ivanpauno
commented
2 years ago building with clang 10 is passing in the nightly builds, e.g. https://ci.ros2.org/view/nightly/job/nightly_linux_clang_libcxx/989/consoleFull#console-section-324.
did you set llvm-config correctly? (see comment here)
(it might not be working for foxy as reported in this ticket, but it should be working when building rolling from src in Ubuntu 20)
vilkun
commented
2 years ago Smth got it working. I'm trying to build ros2-foxy from sources https://docs.ros.org/en/rolling/Installation/Ubuntu-Development-Setup.html with exact clang 11 toolchain.
I installed clang11: sudo apt install clang-11 --install-suggests
to check installation: clang-11 --version clang++-11 --version
I created symbol link: sudo ln -s /usr/lib/llvm-11/bin/llvm-config /usr/bin/llvm-config (Because in /usr/bin was only llvm-config-11 symbol link (wich points there), and no llvm-config file)
After that almost all packages have built (on a second run, it's even more correctly builded) cd ~/ros2_foxy/ rm -r build install log export CC=clang-11 export CXX=clang++-11 colcon build --cmake-force-configure ... So only this packages left with error, but I don't mind: Summary: 311 packages finished [1min 22s] 5 packages had stderr output: rmw_connext_cpp rmw_connext_shared_cpp ros1_bridge rosidl_typesupport_connext_c rosidl_typesupport_connext_cpp
continue above. will try later with: colcon build --symlink-install
quarkytale
commented
1 year ago I'm facing the same issue while building qt_gui_cpp (branch humble) on Humble and Ubuntu 20.04.
umbnich
commented
1 year ago Me too. qt_gui_cpp build fail
asimonov
commented
1 year ago i am seeing same issue building Humble from source on ubuntu20
vineet131
commented
1 year ago Just commenting to say this still exists and I am also getting this same issue today.
Could it be possible because I have ROS Noetic and ROS Galactic on my system? Even though I only source Galactic at build time. Edit: I am using Ubuntu 20.04
gorghino
commented
1 year ago +1 with Humble and Ubuntu 20.04 built by sources:
nvidia@nvidia-orin-rt:~/ros2_humble$ colcon build --merge-install --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo
Starting >>> qt_gui
Starting >>> qt_dotgraph
Starting >>> qt_gui_py_common
Finished <<< qt_gui_py_common [3.51s]
Finished <<< qt_gui [3.61s]
Starting >>> qt_gui_cpp
Starting >>> rqt_gui
Starting >>> qt_gui_app
Starting >>> rqt_py_common
Finished <<< qt_dotgraph [4.56s]
Finished <<< rqt_gui [1.94s]
Starting >>> rqt_gui_py
Finished <<< qt_gui_app [3.24s]
Finished <<< rqt_gui_py [1.80s]
Starting >>> rqt_graph
Finished <<< rqt_graph [2.54s]
Finished <<< rqt_py_common [12.4s]
[Processing: qt_gui_cpp]
[Processing: qt_gui_cpp]
--- stderr: qt_gui_cpp
qt.shiboken: (typesystem) Unable to locate Clang's built-in include directory (neither by checking the environment variables LLVM_INSTALL_DIR, CLANG_INSTALL_DIR nor running llvm-config). This may lead to parse errors.
(typesystem) clang_parseTranslationUnit2(0x0, cmd[26]=-fPIC -Wno-constant-logical-operand -std=c++14 -I/home/nvidia/ros2_humble/src/qt_gui_core/qt_gui_cpp/include -I/home/nvidia/ros2_humble/install/include/pluginlib -I/home/nvidia/ros2_humble/install/include/ament_index_cpp -I/home/nvidia/ros2_humble/install/include/class_loader -I/home/nvidia/ros2_humble/install/include/console_bridge_vendor -I/home/nvidia/ros2_humble/install/include/rcpputils -I/home/nvidia/ros2_humble/install/include/rcutils -I/usr/include -I/usr/include/aarch64-linux-gnu/qt5 -I/usr/include/aarch64-linux-gnu/qt5/QtWidgets -I/usr/include/aarch64-linux-gnu/qt5/QtGui -I/usr/include/aarch64-linux-gnu/qt5/QtCore -I/usr/lib/aarch64-linux-gnu/qt5/mkspecs/linux-g++ -I/usr/include/PySide2 -I/usr/local/cuda/include -I/usr/include/c++/9 -I/usr/include/aarch64-linux-gnu/c++/9 -I/usr/include/c++/9/backward -I/usr/lib/gcc/aarch64-linux-gnu/9/include -I/usr/local/include -I/usr/include/aarch64-linux-gnu -I/usr/include /tmp/global_VzPNvX.hpp)
qt.shiboken: (typesystem) Enum 'RCUTILS_LOG_SEVERITY' does not have a type entry
qt.shiboken: (typesystem) While traversing QOpenGLShaderProgram: setAttributeArray(int,const float*,int,int): Cannot use parameter 2 as an array: <array> modification already applied.
qt.shiboken: (typesystem) class 'QAccessibleWidget' inherits from unknown base class 'QAccessibleActionInterface'
qt.shiboken: (typesystem) class not found for setup inheritance 'QAccessibleActionInterface'
---
Finished <<< qt_gui_cpp [1min 13s]
Starting >>> rqt_gui_cpp
Starting >>> qt_gui_core
Finished <<< qt_gui_core [2.63s]
Finished <<< rqt_gui_cpp [29.7s]
Starting >>> rqt
Finished <<< rqt [1.64s]
Summary: 12 packages finished [1min 48s]
1 package had stderr output: qt_gui_cppnvidia@nvidia-orin-rt:~/ros2_humble$ clang --version
clang version 10.0.0-4ubuntu1
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
KatherineZT
commented
9 months ago In my Dockerfile, compiling Humble on Ubuntu Jammy (22.04), I got it working by installing clang-14 :
RUN sudo apt update -y \
&& sudo apt install clang-14 --install-suggests -y \
&& sudo ln -s /usr/lib/llvm-14/bin/llvm-config /usr/bin/llvm-config
ENV CC=clang-14
ENV CXX=clang++-14Thanks to the comment from @vilkun
qt_gui_core seems to have problems with Clang.
Ubuntu Focal / ROS Master from source
It builds under GCC, though with the following warning about Clang (even though it shouldn't be using Clang at all and llvm-config for the active clang version is in my
$PATH):Under Clang 9, I get warnings:
Under Clang 10 (and 11), I get build errors: