Hi Peter! I almost lost this e-mail, redirectin the thread to pkg-kde-talk as 
that's a better place for this to happen :)

On Saturday 06 September 2014 03:53:54 peter green wrote:
> Qtbase-opensource-src 5.3.1+dfsg-6 failed to build on arm64 (both
> debian-ports and debian official) with the following error
> g++ -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined
> -Wl,-e,qt_core_boilerplate -Wl,-O1 -shared -Wl,-Bsymbolic-functions
> -Wl,--dynamic-list,/«BUILDDIR»/qtbase-opensource-src-5.3.1+dfsg/src/corelib
> /QtCore.dynlist -Wl,-soname,libQt5Core.so.5 -o libQt5Core.so.5.3.1
> -ldl -lgthread-2.0 -pthread -lglib-2.0 -lrt .obj/qcryptographichash.o: In
> function `__bswap_32':
> /usr/include/aarch64-linux-gnu/bits/byteswap.h:46: undefined reference to
> `MD5Context::MD5Context()' collect2: error: ld returned 1 exit status
> Version 5.6.1-3 failed on debian official with a similar error but
> succeeded on debian-ports.
> /usr/include/aarch64-linux-gnu/bits/byteswap.h:46: undefined reference to
> `SHA256Context::SHA256Context()' collect2: error: ld returned 1 exit status
> This along with the lack of any obvious arm64 related stuff in the
> changelog suggests that the failure is likely to have been triggered by
> a build enrivonment change rather than a change in qtbase-opensource-src

I suspect so, but the truth is that arm64 is not being properly detected as an 
arch by Qt. That might help or not. I'm currently preparing the last Qt5 
transition and after that I'll come back to this in a porterbox.

> The error strikes me as plain strange, why the hell would a byteswap
> function be reffering to a crypto hash type. Anyone have any thoughts on
> what might be going on?

Aurelien reviewed it and also didn't have an idea :-/

Of course any hint/idea is appreciated.

Lisandro Damián Nicanor Pérez Meyer

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply via email to