Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. SLES 11 sp3 and Qt5 compilation problems
Forum Updated to NodeBB v4.3 + New Features

SLES 11 sp3 and Qt5 compilation problems

Scheduled Pinned Locked Moved Installation and Deployment
18 Posts 4 Posters 7.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    nicolasg
    wrote on last edited by
    #3

    All the available dependencies from SLES 11 are there but it is an old version and so the package, for xcb, for example are not recent enough. I did as indicate in the RHEL tutorial but I still have some problem. I wanted to know if anyone has a solution to solve them.

    I am completely aware that SLES 11 is old but I do not have any choice, there are hardware sell today with this system and so I do think that it should be possible to compile Qt5 on it but I completely understand the need to use mode modern technology. As mention in my previous message, if I can't compile for this system that means that I have either way to stick to Qt4 or, and I am afraid for it, that the other people in the project will push for something a little bit more portable ie java...

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #4

      I may be wrong, but it seems that you are linking against the system library and not your custom one.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • P Offline
        P Offline
        pwbert
        wrote on last edited by
        #5

        This Thread seems to have stopped without a resolution. I am also getting the same error: Has anyone resolved this issue yet..

        /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_unlock_io’ /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_lock_io’

        I have tried installing libxcb-1.11 and its dependencies in an alternate include and Lib folders and then using the -I and _L options on the configure line. I have all the required dependencies installed. I'm not sure where to go from here. I too am using SLES 11 SP3. The QT versions I have tried building are QT 5.0.2 and 5.4., both get the same error.

        If you have any more ideas I can try to get QT 5 working with SLES 11 SP3 please let me know.

        Thank you ,

        Phil

        1 Reply Last reply
        0
        • P Offline
          P Offline
          pwbert
          wrote on last edited by
          #6

          This Thread seems to have stopped without a resolution. I am also getting the same error: Has anyone resolved this issue yet..

          /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_unlock_io’ /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_lock_io’

          I have tried installing libxcb-1.11 and its dependencies in an alternate include and Lib folders and then using the -I and _L options on the configure line. I have all the required dependencies installed. I'm not sure where to go from here. I too am using SLES 11 SP3. The QT versions I have tried building are QT 5.0.2 and 5.4., both get the same error.

          If you have any more ideas I can try to get QT 5 working with SLES 11 SP3 please let me know.

          Thank you ,

          Phil

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #7

            Hi and welcome to devnet,

            Are you sure that your custom libxcb gets detected ? You can use the -v option to see what the test does

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #8

              Hi and welcome to devnet,

              Are you sure that your custom libxcb gets detected ? You can use the -v option to see what the test does

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • P Offline
                P Offline
                pwbert
                wrote on last edited by
                #9

                I'm pretty sure it is looking at the custom libxcb as after I set that up the compile went much further. I'm not sure what you mean by the "-v" option. I put verbose on the configure and I did not get any more information. This is where it dies:

                make[3]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene' make[3]: Entering directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene'
                g++ -m64 -Wl,-O1 -Wl,-rpath,/udlnas/users/talbepw/qt_5_0_2/build/lib -Wl,-rpath-link,/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtjsbackend/lib -o ../../bin/qmlscene .obj/release-shared/main.o -L/usr/X11R6/lib64 -L/udlnas/users/talbepw/qt_5_0_2/build/lib -L/udlnas/users/talbepw/qt_5_0_2/build/lib64 -L/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/lib -lQt5Quick -L/udlnas/users/talbepw/qt_5_0_2/build//lib -lQt5Qml -L/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtbase/lib -lQt5Widgets -lQt5Network -lQt5Gui -lQt5Core -lGL -lpthread
                /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_unlock_io' /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_lock_io'
                collect2: error: ld returned 1 exit status
                make[3]: *** [../../bin/qmlscene] Error 1
                make[3]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene' make[2]: *** [sub-qmlscene-make_first] Error 2 make[2]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools'
                make[1]: *** [sub-tools-make_first] Error 2
                make[1]: Leaving directory `/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative'
                make: *** [module-qtdeclarative-make_first] Error 2

                Thank you for the help,

                Phil

                1 Reply Last reply
                0
                • P Offline
                  P Offline
                  pwbert
                  wrote on last edited by
                  #10

                  I'm pretty sure it is looking at the custom libxcb as after I set that up the compile went much further. I'm not sure what you mean by the "-v" option. I put verbose on the configure and I did not get any more information. This is where it dies:

                  make[3]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene' make[3]: Entering directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene'
                  g++ -m64 -Wl,-O1 -Wl,-rpath,/udlnas/users/talbepw/qt_5_0_2/build/lib -Wl,-rpath-link,/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtjsbackend/lib -o ../../bin/qmlscene .obj/release-shared/main.o -L/usr/X11R6/lib64 -L/udlnas/users/talbepw/qt_5_0_2/build/lib -L/udlnas/users/talbepw/qt_5_0_2/build/lib64 -L/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/lib -lQt5Quick -L/udlnas/users/talbepw/qt_5_0_2/build//lib -lQt5Qml -L/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtbase/lib -lQt5Widgets -lQt5Network -lQt5Gui -lQt5Core -lGL -lpthread
                  /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_unlock_io' /usr/lib64/libxcb-xlib.so.0: undefined reference to _xcb_lock_io'
                  collect2: error: ld returned 1 exit status
                  make[3]: *** [../../bin/qmlscene] Error 1
                  make[3]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools/qmlscene' make[2]: *** [sub-qmlscene-make_first] Error 2 make[2]: Leaving directory /udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative/tools'
                  make[1]: *** [sub-tools-make_first] Error 2
                  make[1]: Leaving directory `/udlnas/users/talbepw/qt_5_0_2/qt-everywhere-opensource-src-5.0.2/qtdeclarative'
                  make: *** [module-qtdeclarative-make_first] Error 2

                  Thank you for the help,

                  Phil

                  1 Reply Last reply
                  0
                  • SGaistS Offline
                    SGaistS Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on last edited by
                    #11

                    I meant

                    @configure -v the rest of your options@

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    0
                    • SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #12

                      I meant

                      @configure -v the rest of your options@

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      1 Reply Last reply
                      0
                      • M Offline
                        M Offline
                        MarkNH
                        wrote on last edited by
                        #13

                        I just spent 2 weeks tweaking the configuration files and mkspecs to get Qt 5.4.0 to build on SUSE SLED 11. Our machine does not have the SP1 or 2 or 3 so it is much older that what you are using...
                        [gcc 4.3.2 tool chain]

                        I did make sure all the tools were there - python, ruby and the ICU dependency for QtWebKit.
                        The configure command was:
                        ./configure -commercial -confirm-license -platform linux-g++-32 -qt-xcb -no=gtkstyle -prefix /usr/local/Qt-5.4.0 -nomake examples -nomake tests

                        I modified the mkspeck/common/g++-base.conf to change -std=c++0x to c++98 ( I think configure -no-c++11 does the same thing)
                        added -march=pentium4

                        Added DEFINES += GLX_GLXEXT_LEGACY to qtbase/src/plugins/platforms/offscreen/offscreen.pro.

                        Had to create a compatibility header file for definitions to build XCB as a static library, copying the local xcb_atom.h to qtbase/src/3rdparty/xcb/include
                        edit xcb_iccm.h to include <xcb/xcb_stom.h> and <xcb/xcb_compat.h>
                        When building qdeclaritive /src/qml - modified the Makefile to remove -fvisibility=hidden and -finline=hidden
                        force compiler to uses ICU_UNICODE - edit qwebkit/Source/WTF/wtf/platform.h to define it always...
                        removed wchar_unicode from .qmake_conf also.
                        some generated assembly code did not assemble - hand fixed that
                        So I got the build to succeed and ran make install to place everything in the prefix location... DBus libraries did not install - copied them manually...

                        Good news it built -
                        Bad news - assistant, designer fail to run with the following error: QXcbConnection:Failed to get primary output of screen
                        arguments to dbus_message_new_method_call() were incorrect...

                        Not sure where to go from here...

                        1 Reply Last reply
                        0
                        • M Offline
                          M Offline
                          MarkNH
                          wrote on last edited by
                          #14

                          I just spent 2 weeks tweaking the configuration files and mkspecs to get Qt 5.4.0 to build on SUSE SLED 11. Our machine does not have the SP1 or 2 or 3 so it is much older that what you are using...
                          [gcc 4.3.2 tool chain]

                          I did make sure all the tools were there - python, ruby and the ICU dependency for QtWebKit.
                          The configure command was:
                          ./configure -commercial -confirm-license -platform linux-g++-32 -qt-xcb -no=gtkstyle -prefix /usr/local/Qt-5.4.0 -nomake examples -nomake tests

                          I modified the mkspeck/common/g++-base.conf to change -std=c++0x to c++98 ( I think configure -no-c++11 does the same thing)
                          added -march=pentium4

                          Added DEFINES += GLX_GLXEXT_LEGACY to qtbase/src/plugins/platforms/offscreen/offscreen.pro.

                          Had to create a compatibility header file for definitions to build XCB as a static library, copying the local xcb_atom.h to qtbase/src/3rdparty/xcb/include
                          edit xcb_iccm.h to include <xcb/xcb_stom.h> and <xcb/xcb_compat.h>
                          When building qdeclaritive /src/qml - modified the Makefile to remove -fvisibility=hidden and -finline=hidden
                          force compiler to uses ICU_UNICODE - edit qwebkit/Source/WTF/wtf/platform.h to define it always...
                          removed wchar_unicode from .qmake_conf also.
                          some generated assembly code did not assemble - hand fixed that
                          So I got the build to succeed and ran make install to place everything in the prefix location... DBus libraries did not install - copied them manually...

                          Good news it built -
                          Bad news - assistant, designer fail to run with the following error: QXcbConnection:Failed to get primary output of screen
                          arguments to dbus_message_new_method_call() were incorrect...

                          Not sure where to go from here...

                          1 Reply Last reply
                          0
                          • P Offline
                            P Offline
                            pwbert
                            wrote on last edited by
                            #15

                            The output I posted was with using the configure -v option.

                            Phil

                            1 Reply Last reply
                            0
                            • P Offline
                              P Offline
                              pwbert
                              wrote on last edited by
                              #16

                              The output I posted was with using the configure -v option.

                              Phil

                              1 Reply Last reply
                              0
                              • P Offline
                                P Offline
                                pwbert
                                wrote on last edited by
                                #17

                                This is the configure command I'm using:

                                qt_5_0_2/qt-everywhere-opensource-src-5.0.2> ./configure -v --prefix=/udlnas/users/talbepw/qt_5_0_2/build/ -no-c++11 -I/udlnas/users/talbepw/qt_5_0_2/build/include -nomake tests -L/udlnas/users/talbepw/qt_5_0_2/build/lib -continue -L/udlnas/users/talbepw/qt_5_0_2/build/lib64

                                I also tried the "QT-xcb" option - but I get the same error.

                                Thank you,

                                Phil

                                1 Reply Last reply
                                0
                                • P Offline
                                  P Offline
                                  pwbert
                                  wrote on last edited by
                                  #18

                                  This is the configure command I'm using:

                                  qt_5_0_2/qt-everywhere-opensource-src-5.0.2> ./configure -v --prefix=/udlnas/users/talbepw/qt_5_0_2/build/ -no-c++11 -I/udlnas/users/talbepw/qt_5_0_2/build/include -nomake tests -L/udlnas/users/talbepw/qt_5_0_2/build/lib -continue -L/udlnas/users/talbepw/qt_5_0_2/build/lib64

                                  I also tried the "QT-xcb" option - but I get the same error.

                                  Thank you,

                                  Phil

                                  1 Reply Last reply
                                  0

                                  • Login

                                  • Login or register to search.
                                  • First post
                                    Last post
                                  0
                                  • Categories
                                  • Recent
                                  • Tags
                                  • Popular
                                  • Users
                                  • Groups
                                  • Search
                                  • Get Qt Extensions
                                  • Unsolved