port Qt5.13.0 to ARM aarch64 failed

[SGaist]

Hi,

What do you mean by port ?
What configuration options did you use ?

Ubuntu through Debian already provides a Qt port for arm64.

[LengJianHanShuang]

@sgaist
I want to compile and install qt5.13 in my arm board,but during make the above error happened
. I look.through the qt code, the macro "QT_LINUX_FUTEX" will decide to use lockinternal
in qmutex.cpp or in qmutex_linux.cpp , it seems impossible to use both of them, how do you think
. By the way, I am outside now, I don't think it is relative to my configuration, I WILL send to
you later

[Tom_H]

This post is deleted!

[LengJianHanShuang]

@sgaist
Hi,the following is my configure, please have a check

#!/bin/sh

../qt-everywhere-src-5.13.0/configure
-v
-prefix /usr/local/qt5.13
-opensource
-confirm-license
-shared
-release
-make libs
-xplatform linux-aarch64-gnu-g++
-no-opengl
-linuxfb
-qt-libjpeg
-qt-libpng
-qt-zlib
-no-openssl
-no-cups
-no-glib
-no-iconv
-no-system-proxies
-no-separate-debug-info
-nomake examples -nomake tools -nomake tests
-no-pkg-config
-skip qtdeclarative
-skip qtlocation
-skip qtpurchasing
-skip qtwayland
-skip qtwebchannel
-skip qtwebengine
-skip qtwebsockets
-skip qtwebview
-skip qtwebglplugin
-skip qtandroidextras
-skip qtgamepad
-skip qtmacextras
-skip qtwinextras
-skip qtsensors
-skip qtconnectivity
-recheck-all

[LengJianHanShuang]

Anyone who had the same situation please help? How should I know what has led to this problem

[SGaist]

Are you compiling or cross-compiling ?

[LengJianHanShuang]

@sgaist
I directly compiling on the board .

[LengJianHanShuang]

This post is deleted!

[Pablo J. Rogina]

@lengjianhanshuang said in port Qt5.13.0 to ARM aarch64 failed:

Hi,the following is my configure

Could you please also post the output of the configure step?

[SGaist]

The why use the xplatform option ?

[LengJianHanShuang]

@sgaist
Hi, thanks for your reply. I use xplatform as I read from the document that xplatform is the same with -device and -device-option.
Yestoday, I found maybe it is because of the compiler, as qmutex.cpp include "qmutex_linux.cpp", the content of qmutex_linux.cpp will be part of qmutex.cpp, at the same time, the thread.pro has included qmutex_linux into SOURCES also, so there is same content from the two files(qmutex.cpp and qmutex_linux.cpp）

[LengJianHanShuang]

@pablo-j-rogina
Hi the following is the output of my configure, please have a check
---------------------------------Configure summary:

Building on: linux-g++ (arm64, CPU features: neon)
Building for: linux-aarch64-gnu-g++ (arm64, CPU features: neon)
Target compiler: gcc 5.4.0
Configuration: cross_compile compile_examples enable_new_dtags largefile neon shared rpath release c++11 c++14 concurrent dbus no-pkg-config reduce_exports stl
Build options:
Mode ................................... release
Optimize release build for size ........ no
Building shared libraries .............. yes
Using C standard ....................... C11
Using C++ standard ..................... C++14
Using ccache ........................... no
Using new DTAGS ........................ yes
Using precompiled headers .............. no
Using LTCG ............................. no
Target compiler supports:
NEON ................................. yes
Build parts ............................ libs
Qt modules and options:
Qt Concurrent .......................... yes
Qt D-Bus ............................... yes
Qt D-Bus directly linked to libdbus .... no
Qt Gui ................................. yes
Qt Network ............................. yes
Qt Sql ................................. yes
Qt Testlib ............................. yes
Qt Widgets ............................. yes
Qt Xml ................................. yes
Support enabled for:
Using pkg-config ....................... no
udev ................................... no
Using system zlib ...................... no
Zstandard support ...................... no
Qt Core:
DoubleConversion ....................... yes
Using system DoubleConversion ........ no
GLib ................................... no
iconv .................................. no
ICU .................................... no
Built-in copy of the MIME database ..... yes
Tracing backend ........................ <none>
Logging backends:
journald ............................. no
syslog ............................... no
slog2 ................................ no
Using system PCRE2 ..................... no
Qt Network:
getifaddrs() ........................... yes
IPv6 ifname ............................ yes
libproxy ............................... no
Linux AF_NETLINK ....................... yes
OpenSSL ................................ no
Qt directly linked to OpenSSL ........ no
OpenSSL 1.1 ............................ no
DTLS ................................... no
OCSP-stapling .......................... no
SCTP ................................... no
Use system proxies ..................... no
Qt Gui:
Accessibility .......................... yes
FreeType ............................... yes
Using system FreeType ................ no
HarfBuzz ............................... yes
Using system HarfBuzz ................ no
Fontconfig ............................. no
Image formats:
GIF .................................. yes
ICO .................................. yes
JPEG ................................. yes
Using system libjpeg ............... no
PNG .................................. yes
Using system libpng ................ no
EGL .................................... no
OpenVG ................................. no
OpenGL:
Desktop OpenGL ....................... no
OpenGL ES 2.0 ........................ no
OpenGL ES 3.0 ........................ no
OpenGL ES 3.1 ........................ no
OpenGL ES 3.2 ........................ no
Vulkan ................................. no
Session Management ..................... yes
Features used by QPA backends:
evdev .................................. yes
libinput ............................... no
INTEGRITY HID .......................... no
mtdev .................................. no
tslib .................................. no
xkbcommon .............................. no
X11 specific:
XLib ................................. yes
XCB Xlib ............................. no
EGL on X11 ........................... no
QPA backends:
DirectFB ............................... no
EGLFS .................................. no
LinuxFB ................................ yes
VNC .................................... yes
Mir client ............................. no
Qt Sql:
SQL item models ........................ yes
Qt Widgets:
GTK+ ................................... no
Styles ................................. Fusion Windows
Qt PrintSupport:
CUPS ................................... no
Qt Sql Drivers:
DB2 (IBM) .............................. no
InterBase .............................. no
MySql .................................. no
OCI (Oracle) ........................... no
ODBC ................................... no
PostgreSQL ............................. no
SQLite2 ................................ no
SQLite ................................. yes
Using system provided SQLite ......... no
TDS (Sybase) ........................... no
Qt Testlib:
Tester for item models ................. yes
Qt SerialBus:
Socket CAN ............................. yes
Socket CAN FD .......................... yes
SerialPort Support ..................... yes
Further Image Formats:
JasPer ................................. no
MNG .................................... no
TIFF ................................... yes
Using system libtiff ................. no
WEBP ................................... yes
Using system libwebp ................. no
Qt 3D GeometryLoaders:
Autodesk FBX ........................... no
QtXmlPatterns:
XML schema support ..................... yes
Qt Multimedia:
ALSA ................................... no
GStreamer 1.0 .......................... no
GStreamer 0.10 ......................... no
Video for Linux ........................ yes
OpenAL ................................. no
PulseAudio ............................. no
Resource Policy (libresourceqt5) ....... no
Windows Audio Services ................. no
DirectShow ............................. no
Windows Media Foundation ............... no
Qt Tools:
QDoc ................................... no

Note: Also available for Linux: linux-clang linux-icc

Note: The following modules are not being compiled in this configuration:
3dcore
3drender

WARNING: QDoc will not be compiled, probably because libclang could not be located. This means that you cannot build the Qt documentation.

Either ensure that llvm-config is in your PATH environment variable, or set LLVM_INSTALL_DIR to the location of your llvm installation.
On Linux systems, you may be able to install libclang by installing the libclang-dev or libclang-devel package, depending on your distribution.
On macOS, you can use Homebrew's llvm package.
On Windows, you must set LLVM_INSTALL_DIR to the installation path.

Qt is now configured for building. Just run 'make'.
Once everything is built, you must run 'make install'.
Qt will be installed into '/usr/local/qt5.13'.

Prior to reconfiguration, make sure you remove any leftovers from
the previous build.

[LengJianHanShuang]

This topic has been solved in another topic about multiple definition of QBasicMutex::lockInternal

[Pablo J. Rogina]

@lengjianhanshuang great, two things though:

1. could you provide a link here to topic
2. please don't forget to mark your post as solved.

[LengJianHanShuang]

@pablo-j-rogina
ok,thanks for you advice.
about the anser everybody can reference to "https://forum.qt.io/topic/106050/qmutex_linux-cpp-multiple-definition-of-qbasicmutex-lockinternal-int"

[LengJianHanShuang]

@pablo-j-rogina
But I can't mark this topic as solved....
there is no such operation to be selected. so must I delete it?

[SGaist]

No, taken a look at the "Topic Tools" button.