[QtMoko] Error compiling on wheezy

Giacomo 'giotti' Mariani giacomomariani at yahoo.it
Thu Nov 8 16:50:03 CET 2012


Hello Radeck, everyone,
   I successfully built QtMoko in chroot on a Squeeze VirtualBox machine
with target PC :-)

...but now I can't run it: what do you mean by

    * Now switch to first console (CTRL+ALT+F1) and run it:

. /opt/qtmoko/qpe.env
qpe
?

If I do it under chroot I get:

qtmoko-chroot:/opt$ qpe
QScreenLinuxFb::connect: No such file or directory
Error opening framebuffer device /dev/fb0
LinuxFb: driver cannot connect
Aborted

The same happens if I do it outside chroot (connecting with ssh -Y):

$ . /opt/qtmoko/qpe.env
jack at QtDebian:/home/jack$ export
LD_LIBRARY_PATH=/home/jack/qtm/qtmoko-chroot/usr/lib/:/home/jack/qtm/build-pc/image/lib/:/home/jack/qtm/qtmoko-chroot/lib/
jack at QtDebian:/home/jack$ qpe
QScreenLinuxFb::connect: No such file or directory
Error opening framebuffer device /dev/fb0
LinuxFb: driver cannot connect
Aborted


Indeed, I miss /dev/fb0. Where can i get it?

Thanks a lot and best regards,
  Giacomo

PS I would change the README as follow:  

$ git diff
diff --git a/README b/README
index 7868bf2..9bcbf83 100644
--- a/README
+++ b/README
@@ -120,8 +120,11 @@ PC build
     * It's now possible to build QtMoko for x86 without cross
compiling. This
     is great for development. Just do:

+mkdir -p /root/qte/build-pc
+cd /root/qte/build-pc
 ../qtmoko/configure -device pc
 make
+export LD_LIBRARY_PATH=/root/qte/build-pc/qtopiacore/host/lib/
 make install

     * To run the image you need to be root and symlink the result image
to opt:
diff --git a/qtopiacore/qt b/qtopiacore/qt
--- a/qtopiacore/qt
+++ b/qtopiacore/qt
@@ -1 +1 @@
-Subproject commit a5c5ee0bbe93b3fab92d669576776b663f567cef
+Subproject commit a5c5ee0bbe93b3fab92d669576776b663f567cef-dirty


-- 
##############################################################
giacomo 'giotti' mariani
gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859
O< ASCII ribbon campaign: stop HTML mail
www.asciiribbon.org
##############################################################




More information about the community mailing list