Welcome to raspberry-pi-cross-compilers Discussions!

[abhiTronix]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[PaulPaulaner]

Hi,
I hope this is the right place for my Question.
I start with a blank PC (UBUNTU 20.04) and do your instruction step by step.
Cross-Compiling works with no problems.

But when I will compile my project I get the error sys/cdefs.h:No such file or directory
Do I forgot something to install before cross-compile?
I found the header on some places on my PC, is there a wrong link?

Thank you for helping hand and the instruction.

kind regards
Paul

[abhiTronix]

Hey @PaulPaulaner. I'll help with this error. Can you explain what exact steps you took to compile your project? Also, if possible, please share the project you're trying to compile.

[PaulPaulaner]

Dear Abhishek, thank you for your fast response. I do the steps from your instruction and then I configurate the QT Creator (see the pictures attached). If you need more please let it know me. Thank you!

[abhiTronix]

I do the steps from your instruction and then I configurate the QT Creator

@PaulPaulaner So you're using QT Creator instead of following this document: https://github.com/abhiTronix/raspberry-pi-cross-compilers/blob/master/QT_build_instructions.md ?

(see the pictures attached).

No, I cannot see any pictures in your comment. BTW, You cannot attach pictures through email, you need to manually attach them here on GitHub.

[PaulPaulaner]

Hi,
I use this document for cross compile:
https://github.com/abhiTronix/raspberry-pi-cross-compilers/blob/master/QT_build_instructions.md ?

And then I configure QT Creator

[abhiTronix]

Project created by QtCreator 2012-10-16T15:30:31

@PaulPaulaner Is'nt your QT Creator too old? Can you paste the exact version?

error sys/cdefs.h:No such file or directory

Can you paste the output.txt file created by command here: (prints content of sysroot to a text file)

tree /home/hell/rpi-qt/sysroot/ > output.txt

Just drag and drop file into comment to attach it.

[PaulPaulaner]

The QT Creator is the newest version I get, it is a new installation

Qt Creator 4.15.0
Based on Qt 5.15.2 (GCC 7.3.1 20180303 (Red Hat 7.3.1-5), 64 bit)

Here is the output file

output.txt

[abhiTronix]

The QT Creator is the newest version I get, it is a new installation

Qt Creator 4.15.0
Based on Qt 5.15.2 (GCC 7.3.1 20180303 (Red Hat 7.3.1-5), 64 bit)

Here is the output file

output.txt

@PaulPaulaner Everything looks fine. Now add these CMAKE arguments to QTCreator manually [Override wherever necessary]: (See https://doc.qt.io/qtcreator/creator-build-settings-cmake.html)

set(CMAKE_FIND_ROOT_PATH /home/hell/rpi-qt/sysroot)
set(CMAKE_SYSROOT /home/hell/rpi-qt/sysroot)
set(CMAKE_LIBRARY_ARCHITECTURE arm-linux-gnueabihf)
set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -fPIC -Wl,-rpath-link,${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE} -L${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}")
set(CMAKE_C_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -Wl,-rpath-link,${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE} -L${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -Wl,-rpath-link,${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE} -L${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}")
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

and test if it compiles alright, make sure to clean build directory first.

[PaulPaulaner]

Hi at all,
to solve my problem I insert the path directly to the file in my .pro file.
Like this

INCLUDEPATH += /home/<pi?>/rpi-qt/sysroot/usr/include/arm-linux-gnueabihf/

then it works.

Thank you for help and your instruction !

Bye
Paul

[abhiTronix]

@PaulPaulaner Thanks for the heads up. really appreciated. This might help others too, thanks.

[renebokhorst]

I had a similar issue, and I solved it in a similar way. But I think I found where the issue came from. It's from step 10 in the guide; the symbolic links.

sudo ln -sf -r /usr/include/arm-linux-gnueabihf/sys /usr/include
sudo ln -sf -r /usr/include/arm-linux-gnueabihf/openssl /usr/include

these two in particular always fail for me, because the directories already exist. So the symbolic links are never created. And /sys/ happens to be the directory containing cdefs.h.

I was meaning to ask whether you knew a way to without using symbolic links when I found this topic.

Another unrelated issue: Step 8 indirectly looks for openjdk-11-jre-headless. It has some dependencies which are apparently not ready for rpi0 yet. So purging openjdk-11-jre-headless and installing openjdk-8-jre-headless did it for me.

[abhiTronix]

sudo ln -sf -r /usr/include/arm-linux-gnueabihf/sys /usr/include
sudo ln -sf -r /usr/include/arm-linux-gnueabihf/openssl /usr/include

these two in particular always fail for me, because the directories already exist. So the symbolic links are never created. And /sys/ happens to be the directory containing cdefs.h.

@renebokhorst Thanks for sharing your insight. Indeed this is a problem, and I'm yet to find one proper command to create all symbolic links of all files and folders in a directory reliably. Sometimes it works, sometimes it doesn't.

Another unrelated issue: Step 8 indirectly looks for openjdk-11-jre-headless. It has some dependencies which are apparently not ready for rpi0 yet. So purging openjdk-11-jre-headless and installing openjdk-8-jre-headless did it for me.

Thanks I'll update it.

[StuartMellor]

Hi abhiTronix,

I'm trying to cross-compile for the Rasp zero w and struggling with getting a library (portaudio) to compile with the cross-compiler following this guide: https://github-wiki-see.page/m/abhiTronix/raspberry-pi-cross-compilers/wiki/Cross-Compiler-CMake-Usage-Guide-with-rsynced-Raspberry-Pi-32-bit-OS.

My setup:
Ubuntu 20.04 via WSL2 Windows intel 64 Bit -> Raspberry Pi Zero W using Latest Raspberry Pi OS Lite v. 5.10 (2021-05-07-raspios-buster-armhf-lite)

I've managed to get the bare minimum to compile and can confirm that it works on my zero W.

Problem # 1:
At first I came across the error: cannot find crti.o: No such file or directory and then followed your advice to comment out the lines:

      set(CMAKE_SYSROOT ${rootfs_dir})
      set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)

Which solved that problem.

Problem # 2:
On trying to link port audio via my CMakeLists, cmake couldn't find the library file so I used the relative file path: "/usr/local/lib" which I rsynced over from the pi into the "cmake-test/rpi_rootfs/rootfs/usr/" folder, alongside those instructed in the guide (this is the install location of portaudio). Such that my folder structure looks like this:

• cmake-test
• • build
• • rootfs
• • • opt
• • • usr
• • • • include
• • • • lib
• • • • local
• • • • • lib
• • • • • • libportaudio.a
• • • • • • libportaudio.so
• • • • • • libportaudio.so2
            etc...

This solved the problem.

Problem # 3:
Now that it knows where the library is, it's producing this error: libportaudio.a: error adding symbols: file format not recognized. I've also tried the .so library file, but to no avail. I built the library on the Pi zero to save me the headache of trying to cross-compile that and ensure it works with the buster image.

Is it likely to be that by removing the sysroot is the problem here? Or am I being silly and forgetting to add an option? I've trawled the internet and found very little on this problem.

My CMakeLists.txt:

The Error:

My PI.cmake:

[abhiTronix]

Problem # 1:
At first I came across the error: cannot find crti.o: No such file or directory and then followed your advice to comment out the lines:

  set(CMAKE_SYSROOT ${rootfs_dir})
  set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)

Which solved that problem

@renebokhorst This isn't the solution. Problem is somewhere else. Can you first try cross-compiling simple example given in https://github.com/abhiTronix/raspberry-pi-cross-compilers/wiki/Cross-Compiler-CMake-Usage-Guide-with-rsynced-Raspberry-Pi-32-bit-OS#cross-compiler-cmake-usage-guide-with-rsynced-raspberry-pi-32-bit-os doc to narrow down the problem?

Try replicating each step exactly as possible specially check if all symlinks are created successfully since it's the primary reason behind crti.o linkage problem. If you see any error, try #69 (comment)

[StuartMellor]

So, the error continued. I looked into other compilers to see how they configured cmake in the *.cmake file, which you had set in PI.cmake. The error adding symbols: file in wrong format seems to be because cmake still wasn't looking in the right place. It was successfully compiling the binary, but as soon as a program tried to utilise any of the libraries I had linked in the binary wouldn't run at all and produced a different error on the pi. This was the case for pthread, and dl.

I can confirm that this .cmake file sets up the right links for compilation and that pthread, portaudio, dl etc. all are working fully now:
https://github.com/Pro/raspi-toolchain/blob/master/Toolchain-rpi.cmake
(note: a few of the paths need to be altered).

[abhiTronix]

@StuartMellor Can you share your cmake file here?, it might be helpful for others too.

[StuartMellor]

Replacing the PI.cmake file shown in abhiTronix's guide: https://github.com/abhiTronix/raspberry-pi-cross-compilers/wiki/Cross-Compiler-CMake-Usage-Guide-with-rsynced-Raspberry-Pi-32-bit-OS#cross-compiler-cmake-usage-guide-with-rsynced-raspberry-pi-32-bit-os

Replace the lines in
set(LIB_DIRS ... with corresponding absolute paths to your toolchain.

This will set up CMake to compile when using any library files either built on the pi or using the cross-compile toolchain linked as .a or .so files.

i.e.
find_library(PTHREAD pthread PATH $ENV{HOME}/cmake-test/rootfs/ PATH_SUFFIXES .a)
find_library(DL dl PATH $ENV{HOME}/cmake-test/rootfs/ PATH_SUFFIXES .a)
target_link_libraries(cmake_test PUBLIC ${PTHREAD} ${DL})

Note, the following should be distributed with this copyright notice:

 toolchain-raspberry.cmake
 Copyright (C) 2014  Belledonne Communications, Grenoble France



 This program is free software; you can redistribute it and/or
 modify it under the terms of the GNU General Public License
 as published by the Free Software Foundation; either version 2
 of the License, or (at your option) any later version.

 This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.

 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.



 Based on:
 https://gitlab.linphone.org/BC/public/linphone-cmake-builder/blob/master/toolchains/toolchain-raspberry.cmake
 Updated version:
 https://github.com/Pro/raspi-toolchain/blob/master/Toolchain-rpi.cmake

---

if("$ENV{RASPBERRY_VERSION}" STREQUAL "")
	set(RASPBERRY_VERSION 1)
else()
	if($ENV{RASPBERRY_VERSION} VERSION_GREATER 3)
		set(RASPBERRY_VERSION 3)
	else()
		set(RASPBERRY_VERSION $ENV{RASPBERRY_VERSION})
	endif()
endif()

if("$ENV{RASPBIAN_ROOTFS}" STREQUAL "")
	message(FATAL_ERROR "Define the RASPBIAN_ROOTFS environment variable to point to the raspbian rootfs.")
else()
	set(SYSROOT_PATH "$ENV{RASPBIAN_ROOTFS}")
endif()
set(TOOLCHAIN_HOST "arm-linux-gnueabihf")

message(STATUS "Using sysroot path: ${SYSROOT_PATH}")

set(TOOLCHAIN_CC "${TOOLCHAIN_HOST}-gcc")
set(TOOLCHAIN_CXX "${TOOLCHAIN_HOST}-g++")
set(TOOLCHAIN_LD "${TOOLCHAIN_HOST}-ld")
set(TOOLCHAIN_AR "${TOOLCHAIN_HOST}-ar")
set(TOOLCHAIN_RANLIB "${TOOLCHAIN_HOST}-ranlib")
set(TOOLCHAIN_STRIP "${TOOLCHAIN_HOST}-strip")
set(TOOLCHAIN_NM "${TOOLCHAIN_HOST}-nm")

set(CMAKE_CROSSCOMPILING TRUE)
set(CMAKE_SYSROOT "${SYSROOT_PATH}")

set(CMAKE_SYSTEM_NAME "Linux")
if(RASPBERRY_VERSION VERSION_GREATER 1)
	set(CMAKE_SYSTEM_PROCESSOR "armv7")
else()
	set(CMAKE_SYSTEM_PROCESSOR "arm")
endif()


set(CMAKE_C_COMPILER ${TOOLCHAIN_CC})
set(CMAKE_CXX_COMPILER ${TOOLCHAIN_CXX})

set(LIB_DIRS 
         "/home/stuart/cmake-test/tools/cross-pi-gcc-8.3.0-0/arm-linux-gnueabihf/lib" #note these should be replaced by absolute paths to 
          your toolchain
	"/home/stuart/cmake-test/tools/cross-pi-gcc-8.3.0-0/lib" #note these should be replaced by absolute paths to your toolchain
	"${SYSROOT_PATH}/opt/vc/lib"
	"${SYSROOT_PATH}/lib/${TOOLCHAIN_HOST}"
	"${SYSROOT_PATH}/usr/local/lib"
	"${SYSROOT_PATH}/usr/lib/${TOOLCHAIN_HOST}"
	"${SYSROOT_PATH}/usr/lib"
	"${SYSROOT_PATH}/usr/lib/${TOOLCHAIN_HOST}/blas"
	"${SYSROOT_PATH}/usr/lib/${TOOLCHAIN_HOST}/lapack"
)

set(COMMON_FLAGS "-I${SYSROOT_PATH}/usr/include ")
FOREACH(LIB ${LIB_DIRS})
	set(COMMON_FLAGS "${COMMON_FLAGS} -L${LIB} -Wl,-rpath-link,${LIB}")
ENDFOREACH()

set(CMAKE_PREFIX_PATH "${CMAKE_PREFIX_PATH};${SYSROOT_PATH}/usr/lib/${TOOLCHAIN_HOST}")

if(RASPBERRY_VERSION VERSION_GREATER 2)
	set(CMAKE_C_FLAGS "-mcpu=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard ${COMMON_FLAGS}" CACHE STRING "Flags for Raspberry PI 3")
	set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS}" CACHE STRING "Flags for Raspberry PI 3")
elseif(RASPBERRY_VERSION VERSION_GREATER 1)
	set(CMAKE_C_FLAGS "-mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard ${COMMON_FLAGS}" CACHE STRING "Flags for Raspberry PI 2")
	set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS}" CACHE STRING "Flags for Raspberry PI 2")
else()
	set(CMAKE_C_FLAGS "-mcpu=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard ${COMMON_FLAGS}" CACHE STRING "Flags for Raspberry PI 1 B+ Zero")
	set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS}" CACHE STRING "Flags for Raspberry PI 1 B+ Zero")
endif()

set(CMAKE_FIND_ROOT_PATH "${CMAKE_INSTALL_PREFIX};${CMAKE_PREFIX_PATH};${CMAKE_SYSROOT}")

[StuartMellor]

An update!

the PI.cmake file you created does work!

It seems to be that the step:
cmake -DCMAKE_TOOLCHAIN_FILE=~/cmake-test/PI.cmake -DCMAKE_BUILD_TYPE=Debug ..
needs to be repeated when using VSCode in WSL. I think my specific problem lies in my use of a CMake plugin in VSCode which occasionally overrides the cmake configuration for the project and replaces PI.cmake with a default configuration.

If your project isn't compiling, repeat the dcmake_toolchain step to ensure that the PI.cmake file is being used.
Make sure that vs code is set to "No Active Kit" like this:

If the project is compiling but you're having problems getting the binary to run on your PI then check the built file using:
file yourproject_filename

to see if it has been built for the correct architecture:

It should correspond to the pi architecture you're compiling to!
If not, repeat the step:
cmake -DCMAKE_TOOLCHAIN_FILE=~/cmake-test/PI.cmake -DCMAKE_BUILD_TYPE=Debug ..
whilst in your build folder, i.e:

cd ~/cmake-test/build

[abhiTronix]

@StuartMellor Thanks again for the update. Much appreciated.

[StuartMellor]

Okay, so, let's say I wrote a program entirely on my windows PC and I need a library. I link that library using it's .lib file and then add it's includes to the project and then use it in whatever way I need to. Then I compile the project down to an executable and then pass the .dll file to the compiled program so that it has access to the library files.

I also don't want to have to recompile every library that I use on each fresh compile, which could take a while as I intend to use a few math libraries

So, if I'm wanting port this for raspberry pi zero, I should surely be able to link a library file and then compile for that target architecture using the cross compiler? Not, recompile portaudio within the project files. I rebuilt portaudio to make sure I had a binary which worked on the pi as it doesn't seem to run correctly when building using the binaries gernerated on the host.

[abhiTronix]

@StuartMellor Ok do this, follow my steps above and transfer portaudio binaries back to pi. Then, rsync folders again(See Step-6) in host sysroot and run Step-7 to fix relative links, then use that sysroot in your project normally.

[StuartMellor]

Okay. Thanks will try.

[abhiTronix]

This will ensure all portaudio libs are at correct place and don't contain any absolute paths. In my opinion the error are because compiler is picking your host files instead of sysroot.

[StuartMellor]

I'm not sure what's happening with the portaudio binary, but I've managed to get the miniaudio library compiling properly. Thanks for taking the time to test and give advice! I definitely understand the cross-compilation process a lot better now, so thanks for putting the work in!

[HaonPAPA]

Thanks to you, I am compiling the compilation environment by following along.
I am using Raspbian Buster x64 os and gcc is using the cross-gcc-10.3.0-pi_64.tar.gz version.

Project ERROR: Cannot run target compiler '/root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-g++'. Output:
===================
Using built-in specs.
COLLECT_GCC=/root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-g++
aarch64-linux-gnu-g++: error: unrecognized command-line option '-mfpu=crypto-neon-fp-armv8'
aarch64-linux-gnu-g++: error: unrecognized command-line option '-mfloat-abi=hard'
Target: aarch64-linux-gnu
Configured with: ../configure --prefix= --target=aarch64-linux-gnu --enable-languages=c,c++,fortran --with-sysroot=/aarch64-linux-gnu/libc --with-build-sysroot=/tmp/cross-pi-gcc-10.3.0-64/aarch64-linux-gnu/libc --with-arch=armv8-a+fp+simd --disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.3.0 (GCC) 
===================
Maybe you forgot to setup the environment?

But I get an error saying that aarch64-gcc cannot be found. There is no problem with the path. The articles you have compiled are organized based on x84.
How can x64 do it?

../qt-everywhere-src-5.15.2/configure -release -opengl es2 -eglfs -device linux-rasp-pi4-v3d-g++ -device-option CROSS_COMPILE=$(echo $CROSS_COMPILER_LOCATION)/bin/aarch64-linux-gnu- -sysroot ~/rpi-qt/sysroot/ -prefix /usr/local/qt5.15 -extprefix ~/rpi-qt/qt5.15 -opensource -confirm-license -skip qtscript -skip qtwayland -skip qtwebengine -nomake tests -make libs -pkg-config -no-use-gold-linker -v -recheck -L$HOME/rpi-qt/sysroot/usr/lib/aarch64-linux-gnu -I$HOME/rpi-qt/sysroot/usr/include/aarch64-linux-gnu

I'll upload my configure too. Please tell me which part is wrong.

root@devqt-desktop:~/rpi-qt/qt-everywhere-src-5.15.2/qtbase/mkspecs/linux-aarch64-gnu-g++# cat qmake.conf 
#
# qmake configuration for building with aarch64-linux-gnu-g++
#

MAKEFILE_GENERATOR      = UNIX
CONFIG                 += incremental
QMAKE_INCREMENTAL_STYLE = sublib

include(../common/linux.conf)
include(../common/gcc-base-unix.conf)
include(../common/g++-unix.conf)

# modifications to g++.conf
QMAKE_CC                = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-gcc
QMAKE_CXX               = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-g++
QMAKE_LINK              = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-g++
QMAKE_LINK_SHLIB        = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-g++

# modifications to linux.conf
QMAKE_AR                = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-ar cqs
QMAKE_OBJCOPY           = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-objcopy
QMAKE_NM                = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-nm -P
QMAKE_STRIP             = /root/rpi-qt/tools/cross-pi-gcc-10.3.0-64/bin/aarch64-linux-gnu-strip
load(qt_config)

I also tried changing the path of qmake, but the result is the same.

[abhiTronix]

@HaonPAPA You need to make changes to sysroot according to this guide: https://github.com/abhiTronix/raspberry-pi-cross-compilers/wiki/Cross-Compiler-CMake-Usage-Guide-with-rsynced-Raspberry-Pi-64-bit-OS#cross-compiler-cmake-usage-guide-with-rsynced-raspberry-pi-64-bit-os. And there's no need to change qmake.conf.

[abhiTronix]

aarch64-linux-gnu-g++: error: unrecognized command-line option '-mfpu=crypto-neon-fp-armv8'
aarch64-linux-gnu-g++: error: unrecognized command-line option '-mfloat-abi=hard'

Also -march=armv8-a -mfloat-abi=hard -mfpu=neon-fp-armv8 flags not available for ARM64 machines, Use -march=armv8-a+fp+simd flag instead.

[HaonPAPA]

Thank you for answer.
I'm new to Raspberry and I'm also new to Linux. It's very difficult.

I followed the site you recommended. From the Build Dummy Hello-World Project part I don't quite understand. Is the process necessary?
How can I create a CMAKE File if needed? Sorry for asking a very rudimentary question. Shouldn't we also install qt-everywhere-src-5.15.2.tar.xz?

5. I finished up to Fix symbolic links and I downloaded qt-everywhere-src-5.15.2.tar.xz in cmake-test and unpacked it. And I configured configure in cd build, but same error occurred.

../qt-everywhere-src-5.15.2/configure -release -opengl es2  -eglfs -device linux-rasp-pi4-v3d-g++ -device-option CROSS_COMPILE=$(echo $CROSS_COMPILER_LOCATION)/bin/aarch64-linux-gnu- -sysroot ~/rpi-qt/rootfs/ -prefix /usr/local/qt5.15 -extprefix ~/cmake-test/qt5.15 -opensource -confirm-license -skip qtscript -skip qtwayland -skip qtwebengine -nomake tests -make libs -pkg-config -no-use-gold-linker -v -recheck -L$HOME/cmake-test/rootfs/usr/lib/aarch64-linux-gnu -I$HOME/cmake-test/rootfs/usr/include/arm-linux-gnueabihf

Project ERROR: Cannot run target compiler '/root/cmake-test/tools/cross-pi-gcc-8.3.0-64/bin/aarch64-linux-gnu-g++'. Output:
===================
Using built-in specs.
COLLECT_GCC=/root/cmake-test/tools/cross-pi-gcc-8.3.0-64/bin/aarch64-linux-gnu-g++
aarch64-linux-gnu-g++: error: unrecognized command line option '-mfpu=crypto-neon-fp-armv8'
aarch64-linux-gnu-g++: error: unrecognized command line option '-mfloat-abi=hard'
Target: aarch64-linux-gnu
Configured with: ../configure --prefix= --target=aarch64-linux-gnu --enable-languages=c,c++,fortran --with-sysroot=/aarch64-linux-gnu/libc --with-build-sysroot=/tmp/cross-pi-gcc-8.3.0-64/aarch64-linux-gnu/libc --with-arch=armv8-a+fp+simd --disable-multilib
Thread model: posix
gcc version 8.3.0 (GCC) 
===================
Maybe you forgot to setup the environment?

Also -march=armv8-a -mfloat-abi=hard -mfpu=neon-fp-armv8 flags not available for ARM64 machines, Use -march=armv8-a+fp+simd flag instead.

And -march=armv8-a+fp+simd where should I put this option? Can I put it in the configure option?

[HaonPAPA]

Project ERROR: Cannot run target compiler '/root/cmake-test/tools/cross-pi-gcc-8.3.0-64/bin/aarch64-linux-gnu-g++'. Output:
===================
Using built-in specs.
COLLECT_GCC=/root/cmake-test/tools/cross-pi-gcc-8.3.0-64/bin/aarch64-linux-gnu-g++
aarch64-linux-gnu-g++: error: unrecognized command line option '-mfloat-abi=hard'
Target: aarch64-linux-gnu
Configured with: ../configure --prefix= --target=aarch64-linux-gnu --enable-languages=c,c++,fortran --with-sysroot=/aarch64-linux-gnu/libc --with-build-sysroot=/tmp/cross-pi-gcc-8.3.0-64/aarch64-linux-gnu/libc --with-arch=armv8-a+fp+simd --disable-multilib
Thread model: posix
gcc version 8.3.0 (GCC) 
===================
Maybe you forgot to setup the environment?

I tried a second time. This time I tried changing the flag. I modified the qmake.conf file, changed -march=armv8-a+fp+simd and tried to configure again. I get a similar error.