How to build Qt on system without a GUI?

Pavel_47

Hear is after clean and launching make:

constant_mappings.cpp: In function ‘quint64 spiStatesFromQState(QAccessible::State)’:
constant_mappings.cpp:82:35: error: ‘ATSPI_STATE_READ_ONLY’ was not declared in this scope
         setSpiStateBit(&spiState, ATSPI_STATE_READ_ONLY);
                                   ^
Makefile:2911: recipe for target '.obj/constant_mappings.o' failed
make[3]: *** [.obj/constant_mappings.o] Error 1
make[3]: Leaving directory '/home/pavel/qtbase/src/platformsupport/linuxaccessibility'
Makefile:358: recipe for target 'sub-linuxaccessibility-make_first' failed
make[2]: *** [sub-linuxaccessibility-make_first] Error 2
make[2]: Leaving directory '/home/pavel/qtbase/src/platformsupport'
Makefile:585: recipe for target 'sub-platformsupport-make_first' failed
make[1]: *** [sub-platformsupport-make_first] Error 2
make[1]: Leaving directory '/home/pavel/qtbase/src'
Makefile:50: recipe for target 'sub-src-make_first' failed
make: *** [sub-src-make_first] Error 2

jsulm

@Pavel_47 said in How to build Qt on system without a GUI?:

ATSPI_STATE_READ_ONLY

This belongs to libatspi. Do you have it and its dev package in your sysroot for RPi?

Pavel_47

You mean in sysroot/lib/ ?
No at that place there is no libatspi.

Pavel_47

@Pavel_47 said in How to build Qt on system without a GUI?:

libatspi

I've tried to install libatspi and libatspi-dev, but Ubuntu updater couldn't locate these packages. Should they come from synchronization with RPi ?

jsulm

@Pavel_47 said in How to build Qt on system without a GUI?:

Should they come from synchronization with RPi ?

Yes

Pavel_47

So, should I install them on RPi and then re-synchronize ?

Pavel_47

The Raspberry Pi also could not locate these packages.

jsulm

@Pavel_47 My Ubuntu 18.04 has libatspi2.0-0 and libatspi2.0-0-dev
What is running on your RPi?

Pavel_47

My Ubuntu 18.04 has libatspi2.0-0 and libatspi2.0-0-dev
You have them in /usr/lib/ ?

What is running on your RPi?
Raspbian 10 (buster)

Pavel_47

If I understood, you managed to build Qt toolchain for RPi4 on your Ubuntu. Is it correct?

Pavel_47

The execution of one of the 3 resynchronizations (rsync -avz pi@yourpi:/usr/lib sysroot/usr to be exact) resulted in the following error:

sent 1,332,333 bytes received 119,470,015 bytes 1,320,244.24 bytes/sec
total size is 3,341,241,457 speedup is 27.66
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1668) [generator=3.1.2]

It’s probably related to the cause of make failure. I went up the log of synchronization, displayed on the screen but I did not notice any error.

Any suggestions ?

jsulm

@Pavel_47 said in How to build Qt on system without a GUI?:

You have them in /usr/lib/ ?

In /usr/lib/x86_64-linux-gnu/libatspi.so.0
And Ubuntu provides the packages I mentioned above.
Debian should provide them as well (Raspbian is based on Debian), so you should be able to install them.

"Any suggestions ?" - well, something went wrong, there should be something in the log.

Pavel_47

@jsulm said in How to build Qt on system without a GUI?:

Debian should provide them as well (Raspbian is based on Debian), so you should be able to install them.
"Any suggestions ?" - well, something went wrong, there should be something in the log.

Yes I also have it on Ubuntu on the same location.
I also checked on Raspberry: it is there - in /user/lib/arm-linux-gnueabihf
But I didn't find it on Ubuntu - in ~/raspi/sysroot/usr/lib/arm-linux-gnueabihf, the folder which was synchronized with RPi.
Concerning your suggestion to look over log ... I didn't find any log file on rsync instruction. Nevertheless I look through over whole display buffer after erroneuous rsync execution (that didn't contain whole log !!!) and didn't find any error.

SGaist

Hi,

If you can find the libraires/headers in your device root file system then using scp might be faster in your case to ensure you copy the files back to your machine.

Pavel_47

@SGaist said in How to build Qt on system without a GUI?:

Hi,

If you can find the libraires/headers in your device root file system then using scp might be faster in your case to ensure you copy the files back to your machine.

Copied missed libraries from RPi to Ubuntu and rerun build.
Here is as it fails this time:

/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.a(pthread_create.o): In function __pthread_create_2_1': /build/glibc-FUvrFr/glibc-2.28/nptl/pthread_create.c:697: undefined reference to _dl_stack_flags'
/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.a(unwind.o): In function unwind_stop': /build/glibc-FUvrFr/glibc-2.28/nptl/unwind.c:72: undefined reference to __pointer_chk_guard_local'
/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.a(nptl-init.o): In function __pthread_initialize_minimal_internal': /build/glibc-FUvrFr/glibc-2.28/nptl/nptl-init.c:434: undefined reference to _dl_pagesize'
/build/glibc-FUvrFr/glibc-2.28/nptl/nptl-init.c:434: undefined reference to _dl_init_static_tls' /build/glibc-FUvrFr/glibc-2.28/nptl/nptl-init.c:434: undefined reference to _dl_wait_lookup_done'
/home/pavel/raspi/sysroot/usr/lib/arm-linux-gnueabihf/libpthread.a(nptl-init.o): In function __pthread_get_minstack': /build/glibc-FUvrFr/glibc-2.28/nptl/nptl-init.c:443: undefined reference to _dl_pagesize'
collect2: error: ld returned 1 exit status
Makefile:1155: recipe for target '../../lib/libQt5Core.so.5.12.6' failed
make[2]: *** [../../lib/libQt5Core.so.5.12.6] Error 1
make[2]: Leaving directory '/home/pavel/qtbase/src/corelib'
Makefile:198: recipe for target 'sub-corelib-make_first' failed
make[1]: *** [sub-corelib-make_first] Error 2
make[1]: Leaving directory '/home/pavel/qtbase/src'
Makefile:50: recipe for target 'sub-src-make_first' failed
make: *** [sub-src-make_first] Error 2

Pavel_47

I've just tried once more resync the /usr/lib.
... and it failed immediately:

2020/02/14 12:25:34 [7746] receiving file list
2020/02/14 12:25:34 [7749] rsync: send_files failed to open "/usr/lib/cups/backend/vnc": Permission denied (13)
2020/02/14 12:25:38 [7749] sent 5,485 bytes received 1,284,984 bytes 73,741.09 bytes/sec
2020/02/14 12:25:38 [7749] total size is 3,341,241,457 speedup is 2,589.17
2020/02/14 12:25:38 [7746] rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1668) [generator=3.1.2]