Qt online installer for arm64 gives me an error on my Pi5
-
admin@raspberrypi:~/Downloads $ ./qt-online-installer-linux-arm64-4.8.1.run ./qt-online-installer-linux-arm64-4.8.1.run: error while loading shared libraries: libxcb-cursor.so.0: cannot open shared object file: No such file or directory
am running the latest 64bit raspian.
how can i fix this?
-
Hi,
Did you check whether you have that library installed on your system ?
-
it did not occur to me that the installer would be dependant on a non standrad library, but now that you said it, ... i could install the lib with apt and it started LOL
-
-
-
LOL and it crashed with :
/home/admin/Qt/6.8.2/gcc_arm64/bin/qmake" QList("-query") crashed with exit code 11 standard output: "" error output: "
so not quite good -
wonderfull, just wonderfull....and now what LOL
-
Since the other people did not provide the requested stack trace, please do it, it will help.
-
on and how to do it?
-
Since the call to
qmake -query
crashes, start it using the debugger and once it crashes request the backtrace then you can copy it to post it on the bug report. -
and how do i start somethign under a debugger on linux without having qt creator up and running?
sorry windows dev here, we just click buttons and don't use console -
I guess you are running raspbian as your Linux distribution ? If so, you likely have already install the build-essential package which should provide you with gdb.
Then it's:
gdb --args /home/admin/Qt/6.8.2/gcc_arm64/bin/qmake -query
Once you are in gdb, just typerun
and enter. It will call qmake and crash.
Thenbt
and enter and it should show you the backtrace.This quick introduction might give you a good starting point.
-
ok done thanks, lets wait and hope for the best
-
Thanks for the help !
-
The root cause for the problem is that you are using Rasbian, a Debian 12-based distribution, and our binaries are built using Ubuntu 24.04 (our reference platform). And Ubuntu 24.04 has a newer glibc version than Debian12
-
Well but there must be some way around that, cant you link glibc statically into Qt and the installer, AFAIK the Linux kernel tries not to break userspace, so if you link everything statically than that thing should run on a pretty wide range of Linuxes, or not?
-
And you open a new can of worm: what do you do when bugs (especially security issues) are found in glibc ?