SLES 11 sp3 and Qt5 compilation problems
-
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
-
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
-
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 2Thank you for the help,
Phil
-
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 2Thank you for the help,
Phil
-
I meant
@configure -v the rest of your options@
-
I meant
@configure -v the rest of your options@
-
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 testsI 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=pentium4Added 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...
-
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 testsI 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=pentium4Added 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...
-
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
-
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
