Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Trying to fix 2 errors during build for openSuse Leap 15.2



  • While trying to run configure command
    % ./configure -prefix /home/owner/qtbase -opensource

    The following messages appear at the end:

    Note: Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing.
    (this is NOT true, D-Bus is alive in the openSuse Leap 15.2 OS)

    WARNING: QDoc will not be compiled, probably because libclang could not be located. This means that you cannot build the Qt documentation.

    Either ensure that llvm-config is in your PATH environment variable, or set LLVM_INSTALL_DIR to the location of your llvm installation.
    On Linux systems, you may be able to install libclang by installing the libclang-dev or libclang-devel package, depending on your distribution.
    both libclang and libclang development libraries are installed as well as llvm

    I saw that under home/owner/qt-everywhere-src-5.15.2/coin/provisioning, that the folder qtci-linux-openSUSE-15.2-x86_64 is missing, the one for Leap 15.1 is there.

    What can I do to fix the D-Bus and more importantly the clang library problem?

    Thanks for your help.


  • Lifetime Qt Champion

    @Randall-0 said in Trying to fix 2 errors during build for openSuse Leap 15.2:

    What can I do to fix the D-Bus and more importantly the clang library problem?

    Install the dbus development package and if you really need the qdoc stuff (for whatever reason) install llvm-clang as described in the output.



  • I believe that I have installed the dbus and llvm and clang libraries. An output of the zypper -l command shows 56 installed packages:
    i+|dbus-1|D-Bus Message Bus System|package
    i+|dbus-1-devel|Developer package for D-Bus|package
    i+|dbus-1-glib|GLib-based library for using D-Bus|package
    i |dbus-1-glib-devel|Developer package for D-Bus/GLib bindings |package
    i+|dbus-1-glib-tool|Tool package for D-Bus/GLib bindings|package
    i+|dbus-1-x11|D-Bus Message Bus System|package
    i+|dbus-sharp|Managed C# implementation of D-Bus|package
    i+|dbus-sharp-glib|Glib integration for DBus|package
    i+|dleyna-connector-dbus|dLeyna connector interface -- DBus|package
    i+|gmenudbusmenuproxy|GMenu to DBusMenu Proxy|package
    i+|kdbusaddons-tools|Convenience classes for QtDBus: CLI tools|package
    i+|libKF5DBusAddons5-lang|Translations for package kdbusaddons|package
    i+|libdbus-1-3|Library package for D-Bus|package
    i |libdbus-1-3-32bit|Library package for D-Bus |package
    i+|libdbus-c++-1-1|C++ Interface for D-Bus|package
    i+|libdbus-c++-devel|Development files for libdbus-c++|package
    i |libdbus-c++-glib-1-1|Glib integration for libdbus-c++ |package
    i |libdbusmenu-glib-devel|Development files for libdbusmenu-glib |package
    i+|libdbusmenu-glib4|Small library that passes a menu structure across D-Bus|package
    i+|libdbusmenu-gtk3-4|GTK+ 3 version of libdbusmenu|package
    i+|libdbusmenu-jsonloader-devel|Development files for libdbusmenu-jsonloader4|package
    i+|libdbusmenu-jsonloader4|Small library that passes a menu structure across DBus -- Test library|package
    i+|libdbusmenu-qt-devel|Development package for libdbusmenu-qt|package
    i+|libdbusmenu-qt2|Development package for dbusmenu-qt|package
    i+|libdbusmenu-qt5-2|Development package for dbusmenu-qt5|package
    i+|libdbusmenu-qt5-devel|Development package for libdbusmenu-qt5|package
    i+|libdbusmenu-tools|Development tools for the dbusmenu libraries|package
    i+|libeldbus1|ELDbus, part of EFL|package
    i+|libqt5-qdbus|Interface to Qt applications communicating over D-Bus|package
    i+|python2-dbus-python|Python bindings for D-Bus|package
    i+|python3-dbus-python|Python bindings for D-Bus|package
    i+|python3-slip-dbus|Convenience functions for dbus services|package
    i+|ruby2.5-rubygem-ruby-dbus|Ruby module for interaction with D-Bus|package
    i+|system-config-printer-dbus-service|D-Bus service to configure printing via system-config-printer|package
    i |typelib-1_0-Dbusmenu-0_4|Introspection bindings for libdbusmenu-glib4 |package
    i+|xdg-dbus-proxy|Filtering proxy for D-Bus connections|package
    i+|clang9|CLANG frontend for LLVM|package
    i+|clang9-checker|Static code analyzer for CLANG|package
    i+|clang9-devel|CLANG frontend for LLVM (devel package)|package
    i+|clang9-doc|Documentation for Clang|package
    i+|libclang9|Library files needed for clang|package
    i+|texlive-sclang-prettifier|Prettyprinting SuperCollider source code|package
    i+|texlive-sclang-prettifier-doc|Documentation for texlive-sclang-prettifier|package
    i+|llvm|Low Level Virtual Machine|package
    i+|llvm-devel|Header Files for LLVM|package
    i |llvm-gold|Gold linker plugin for LLVM |package
    i |llvm-vim-plugins|Vim plugins for LLVM |package
    i |llvm9|Low Level Virtual Machine |package
    i |llvm9-LTO-devel|Link-time optimizer for LLVM (devel package) |package
    i |llvm9-devel|Header Files for LLVM |package
    i |llvm9-doc|Documentation for LLVM |package
    i |llvm9-gold|Gold linker plugin for LLVM |package
    i |llvm9-polly|LLVM Framework for High-Level Loop and Data-Locality Optimizations |package
    i |llvm9-polly-devel|Development files for Polly |package
    i |llvm9-vim-plugins|Vim plugins for LLVM |package
    i+|python3-llvmlite|Lightweight wrapper around basic LLVM functionality|package

    So I don't think I am missing anything. However the same error keeps reoccurring upon running the configure command.

    Any ideas?


  • Lifetime Qt Champion

    Hi,

    Check the configure tests logs to see exactly how the DBus failed.



  • @SGaist I will do that, but due to the incredible number of compiler and loader crashes, using gcc v7, I realized that something was wrong with the gcc compiler. Hence I completely took my linux system down to the bare metal and fresh installed a brand new OS and I just completed installing gcc v10 which is not supposed to have these wierd crashes (even the loader crashed twice). I have to start fresh with the offline install again, but I am hopeful that v10 of gcc will behave in a more controlled manner. Thanks for telling me to look in the logs. I will do that when I redo this project again.


  • Lifetime Qt Champion

    OpenSuse also provides precompile Qt5.15.2 binaries so why not use those?



  • @Christian-Ehrlicher I might do that, thanks. It's been a long long 2 days, as I had to reinstall openSuse Linux 3 times. My user folder was completely erased, necessitating the 3rd install from ground up, I had NOT had an opportunity to adequately save things from the backup as it was holding older data. Things are all backed up now.



  • After reinstalling the openSuse Leap 15.2 OS, I went back to attempting to build QT-everywhere, which compiled for hours, but crashed on a nss missing package error. This seems to have occurred with linux chromium build, when looking up the error in a search engine. I will concentrate on the nss build problem, hoping to eventually come to success.


  • Lifetime Qt Champion

    @Randall-0
    Wish you good luck and no more reinstalls. :)



  • @mrjj Thanks for the wishes. I am keeping careful track of everything which occurs and documenting which steps (from which QT webpage) I am carefully following. So far I have over 30 hours in these 5 attempts to build QT5 v 5.15.2 but so far success has eluded me. I will keep trying however, but hopefully not flood the forum with the 5,518 lines of errors report and such things ;-)


Log in to reply