[SOLVED] native compile on armel

clogwog

configure: @./configure -v -opensource -confirm-license -icu -qt-xcb -make libs -no-pch -device imx6 -opengl -prefix /opt/qt5.1-armel -device-option CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- @

@make@
then
@make install@

gives me errors as soon as qtdeclarative tries to link:

@/usr/bin/arm-linux-gnueabi-g++ -Wl,-rpath-link,/usr/lib -Wl,--no-undefined -Wl,-O1 -Wl,-rpath,/opt/qt5.1-armel/lib -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQt5Declarative.so.5 -o libQt5Declarative.so.5.1.0 ....... heaps more .....
-L/usr/lib -L/home/falcon/qt-everywhere-opensource-src-5.1.0-clean/qtxmlpatterns/lib -lQt5XmlPatterns -L/home/falcon/qt-everywhere-opensource-src-5.1.0-clean/qtbase/lib -lQt5Widgets -lQt5Network -lQt5Sql -L/home/falcon/qt-everywhere-opensource-src-5.1.0-clean/qtscript/lib -lQt5Script -lQt5Gui -lQt5Core -lpthread -lrt -lQt5XmlPatterns -L/usr/lib -L/home/falcon/qt-everywhere-opensource-src-5.1.0-clean/qtbase/lib -lQt5Network -lQt5Core -lpthread -lGL
.obj/release-shared/qdeclarativeengine.o: In function QDeclarativeEnginePrivate::QDeclarativeEnginePrivate(QDeclarativeEngine*)': qdeclarativeengine.cpp:(.text+0x39b0): undefined reference to QDeclarativeItemModule::defineModule()'
.obj/release-shared/qdeclarativeitemsmodule.o: In function QDeclarativeItemModule::defineModuleCompat()': qdeclarativeitemsmodule.cpp:(.text+0x57c): undefined reference to .LC124'
qdeclarativeitemsmodule.cpp:(.text+0x580): undefined reference to `.LC125'

.... 30 odd more of these LC errors...

qdeclarativeitemsmodule.cpp:(.text+0x630): undefined reference to .LC168' qdeclarativeitemsmodule.cpp:(.text+0x638): undefined reference to .LC169'
qdeclarativeitemsmodule.cpp:(.text+0x63c): undefined reference to .LC124' qdeclarativeitemsmodule.cpp:(.text+0x640): undefined reference to .LC170'
.obj/release-shared/qdeclarativeitemsmodule.o: In function non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>::~QDeclarativeElement()': qdeclarativeitemsmodule.cpp:(.text._ZN19QDeclarativePrivate19QDeclarativeElementI25QDeclarativeAnimatedImageED1Ev[non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>::~QDeclarativeElement()]+0x4): undefined reference to .LTHUNK152'
.obj/release-shared/qdeclarativeitemsmodule.o: In function non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>::~QDeclarativeElement()': qdeclarativeitemsmodule.cpp:(.text._ZN19QDeclarativePrivate19QDeclarativeElementI25QDeclarativeAnimatedImageED1Ev[non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>::~QDeclarativeElement()]+0xc): undefined reference to .LTHUNK153'
.obj/release-shared/qdeclarativeitemsmodule.o: In function QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>::~QDeclarativeElement()': qdeclarativeitemsmodule.cpp:(.text._ZN19QDeclarativePrivate19QDeclarativeElementI25QDeclarativeAnimatedImageED2Ev[_ZN19QDeclarativePrivate19QDeclarativeElementI25QDeclarativeAnimatedImageED5Ev]+0x28): undefined reference to vtable for QDeclarativePrivate::QDeclarativeElement<QDeclarativeAnimatedImage>'
.obj/release-shared/qdeclarativeitemsmodule.o: In function non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeBorderImage>::~QDeclarativeElement()': qdeclarativeitemsmodule.cpp:(.text._ZN19QDeclarativePrivate19QDeclarativeElementI23QDeclarativeBorderImageED1Ev[non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeBorderImage>::~QDeclarativeElement()]+0x4): undefined reference to .LTHUNK148'
.obj/release-shared/qdeclarativeitemsmodule.o: In function non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeBorderImage>::~QDeclarativeElement()': qdeclarativeitemsmodule.cpp:(.text._ZN19QDeclarativePrivate19QDeclarativeElementI23QDeclarativeBorderImageED1Ev[non-virtual thunk to QDeclarativePrivate::QDeclarativeElement<QDeclarativeBorderImage>::~QDeclarativeElement()]+0xc): undefined reference to .LTHUNK149'

... heaps more LTHUNK errors ....
@

what does THUNK mean ?

SGaist

Hi,

From your thread title, something is not very clear, are you cross-compiling Qt ? Or are you building it natively (on your arm device) ?

clogwog

you bring up a good question, because it does look like i am CROSS_COMPILING. i did this because when i originally ran ./configure without those options, it somehow didn't detect the architecture, and configure suggested i'd use the device-option CROSS_COMPILE.. i did and it continues a lot further..

overnight i downloaded 5.1.1 and did exactly the same, and i just ran an example and it works !

but i might have to review my options so i know what is going on. because to be honest, in not sure why this works.

i'll mark it as solved, because it is working :)