ubuntu-phone team mailing list archive

[Robert Schroll <rschroll@xxxxxxxxx>]

On Sun, Jul 6, 2014 at 2:30 PM, Robert Schroll <rschroll@xxxxxxxxx> 
wrote:
> > (click-ubuntu-sdk-14.10-armhf)root@copper:/home/rschroll/touch/beru-arm# 
> > qmake -qt=qt5-arm-linux-gnueabihf
> > qmake: could not exec '/usr/lib/arm-linux-gnueabihf/qt5/bin/qmake': 
> > No such file or directory
> > (click-ubuntu-sdk-14.10-armhf)root@copper:/home/rschroll/touch/beru-arm# 
> > ls -l /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake
> > -rwxr-xr-x 1 root root 2222140 Jul  1 12:37 
> > /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake
>
> ?!

I think I understand this at least:

> (click-ubuntu-sdk-14.10-armhf)root@copper:/home/rschroll# file /bin/ls
> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
> dynamically linked (uses shared libs), for GNU/Linux 2.6.24, 
> BuildID[sha1]=64d095bc6589dd4bfbf1c6d62ae985385965461b, stripped

It looks to me that this armhf chroot is actually a x86_64 chroot.  The 
version of qmake I was trying to run is an arm executable, so this is 
why it was complaining about not finding the file.

Anyway, I've added the PPA, updated, made a new chroot, and all the 
problems seem to persist.

Robert