Installing QT5

Hi,

I am very beginner in the Jetson but I am going to run this command “sudo apt-get install qtbase5-dev qtconnectivity5-dev” but it seems it is not compatible with the Jestson architecture. Does anyone know how I can install qt5 or run that command in my Jetson Xavier ubuntu 18.04. Thanks

Sometimes it is a case of not having the right repository enabled. I haven’t worked with the qt5 components, but I am able to:

# sudo -s
# apt search qtbase5-dev
Sorting... Done
Full Text Search... Done
qtbase5-dev/bionic-updates,now 5.9.5+dfsg-0ubuntu2.3 arm64 [installed]
  Qt 5 base development files

qtbase5-dev-tools/bionic-updates,now 5.9.5+dfsg-0ubuntu2.3 arm64 [installed,automatic]
  Qt 5 base development programs

# apt search qtconnectivity5-dev
Sorting... Done
Full Text Search... Done
qtconnectivity5-dev/bionic 5.9.5-0ubuntu1 arm64
  Qt Connectivity development files

# apt-get install qtbase5-dev qtbase5-dev-tools

So unless you have the wrong qt5 versions (or none), then it should work. Do the above “apt search…” commands show the packages available? If so, then does the above “apt-get install…” work? Note that I used “sudo -s” to drop into a root shell first, but only the “apt-get install…” requires root/sudo.

Thanks so much for your reply. Yeah I see the availability of packages when I run “apt search …” but when I run “apt-get install qtbase5-dev qtbase5-dev-tools” I get an error. Here is the error message:

Err:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 libegl1-mesa-dev arm64 19.0.8-0ubuntu0~18.04.2
404 Not Found [IP: 91.189.88.150 80]
Err:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 libgles2-mesa-dev arm64 19.0.8-0ubuntu0~18.04.2
404 Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/m/mesa/libegl1-mesa-dev_19.0.8-0ubuntu0~18.04.2_arm64.deb 404 Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/m/mesa/libgles2-mesa-dev_19.0.8-0ubuntu0~18.04.2_arm64.deb 404 Not Found [IP: 91.189.88.150 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

My problem was actually fixed. Thanks for your help.

HI, I am facing the same problem as yours , How did you solve this issue

Err:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 libegl1-mesa-dev arm64 19.0.8-0ubuntu0~18.04.2
404 Not Found [IP: 91.189.88.150 80]
Err:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 libgles2-mesa-dev arm64 19.0.8-0ubuntu0~18.04.2
404 Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/m/mesa/libegl1-mesa-dev_19.0.8-0ubuntu0~18.04.2_arm64.deb 404 Not Found [IP: 91.189.88.150 80]
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/pool/main/m/mesa/libgles2-mesa-dev_19.0.8-0ubuntu0~18.04.2_arm64.deb 404 Not Found [IP: 91.189.88.150 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Looks like a problem with your ISP’s dns. You can probably fix your issue by changing your DNS nameservers to something reliable like cloudflare (1.1.1.1) or google (8.8.8.8, and/or 8.8.4.4). Instructions for changing it are here:

https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/

You may also wish to change it at your gateway so as not to have to rely on fail ISP dns. The procedure for doing that differs per gateway.

That’s actually an HTTP code 404, so the server was reached, but the file was not found. Ubuntu’s server is not providing the arm64 version of those packages (at least not that server). I’m not sure what the workaround is for that, but possibly it is just a matter of adding a different repository.

I am thinking it could be the ISP’s cache being out of date since some ISPs will cache apt. That would explain the missing package. That package downloads and installs fine from that same repo for me (actually i got 19.0.8-0ubuntu0~18.04.3).

I am not certain but “-o Acquire::http::proxy=false” added to the apt-get command or in /etc/apt/apt.conf might bypass such an isp proxy.

Otherwise specifying a different download server might work. TBH, I’ve never run into this exact issue myself, but the Ubuntu documentatation states it may help.