[Development] Qt 5.7.0 Toolchain on RasPI2

[Alexander Nassian]

The configure command is:

 ../qt-everywhere-opensource-src-5.7.0/configure -opensource -confirm-license -no-pch -no-xcb -nomake tests -make libs -device linux-rasp-pi2-g++ -nomake examples -device-option CROSS_COMPILE=/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/current_toolchain/arm-linux-gnueabihf- -sysroot /home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs -no-gcc-sysroot -prefix /usr/local/qt-5.7.0 -v

EGLFS and others were disabled because of the already mentioned linker error.

/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/libpthread.so.0: undefined reference to `__mktemp at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/librt.so.1: undefined reference to `__clock_settime at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/librt.so.1: undefined reference to `__clock_getcpuclockid at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/libpthread.so.0: undefined reference to `__call_tls_dtors at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/libpthread.so.0: undefined reference to `__madvise at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/librt.so.1: undefined reference to `__clock_nanosleep at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/libpthread.so.0: undefined reference to `__ctype_init at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/librt.so.1: undefined reference to `__clock_getres at GLIBC_PRIVATE'
/home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-gnueabihf/librt.so.1: undefined reference to `__clock_gettime at GLIBC_PRIVATE’

Please find attached the complete configure log.


Beste Grüße / Best regards,
Alexander Nassian

> Am 19.06.2016 um 21:18 schrieb Thiago Macieira <thiago.macieira at intel.com>:
> 
> On domingo, 19 de junho de 2016 17:44:21 PDT Alexander Nassian wrote:
>> Hi,
>> 
>> Currently I’m doing a 5.7.0 build for RasPI 2 with Raspian using the
>> „official“ toolchain (arm-linux-gnueabihf-g++ (crosstool-NG
>> linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) 4.8.3 20140303 (prerelease)).
>> EGLFS wasn’t detected (don’t need it atm either)
> 
> configure -v output showing why it was discarded missing.
> 
>> and the build stopped with
>> a linker error because of missing clock_gettime in QElapsedTimer. 
> 
> You didn't include the error message. Please include the link command-line 
> too.
> 
>> The
>> common recommendation adding -lrt to the linker options didn’t work because
>> configure will then don’t detect C++11 support. 
> 
> Information missing.
> 
>> I didn’t find anything related in the bug tracker (or maybe I searched the
>> wrong way). For this reason I wanted to ask here if this is a known
>> problem, or a known wrong configuration thing? If not I would be happy to
>> provide configuration, compiler output, etc..
> 
> None of those are known issues.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160619/3fb71807/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: application/octet-stream
Size: 90092 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160619/3fb71807/attachment.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160619/3fb71807/attachment-0001.html>