Re: [QtMoko] Error compiling on wheezy
On Tuesday, December 04, 2012 02:42:18 PM Giacomo 'giotti' Mariani wrote: > Do you have any suggestion? Yes you are missing pulse audio dev package. You should install the packages in README. If you are building for PC then: apt-get install libxext-dev libasound2-dev libdbus-1-dev libssl-dev libts-dev libbluetooth-dev libxtst-dev libpng12-dev libjpeg8-dev libv4l-dev libspeexdsp- dev libglib2.0-dev libsqlite3-dev libgstreamer0.10-dev libgstreamer-plugins- base0.10-dev libpulse-dev libvorbis-dev Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Hi All, following Radek suggestion, I've being able to start QtMoko on the virtual machine: just hat to run it as root. Most of the icons are not working, such as the application menu, which is partially populated. Now, after "git pull", I'm trying to recompile, but I get the following error in ./configure: ERROR: You requested "-sound-system pulse" but it was disabled. Do you have any suggestion? Best, Giacomo On 11/26/2012 06:08 PM, Giacomo 'giotti' Mariani wrote: > Hi all. > > Updates: > * I had to install libasound2 libgstreamer-plugins-base0.10-0 > libts-0.0-0 in order to solve library dependencies. > * I had no mouse in console, so I had to install gpm. > > Now I'm able to run qpe, but: > * the mouse is quite unresponsive. > * the QtMoko calibration window appears, but I'm not able to click and > calibrate it... : > Cannot open input device '/dev/tty0': Permission denied > readFile failed /sys/bus/platform/devices/twl4030_usb/vbus : "No such > file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/status : "No > such file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/capacity : "No > such file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/current_now : > "No such file or directory" > > Any further suggestion? > > Thanks a lot, > Giacomo > > On 11/23/2012 06:11 PM, Giacomo 'giotti' Mariani wrote: >> Hello Frode, Everyone, >> following http://ubuntuforums.org/showthread.php?t=652038 , >> http://frontseed.com/entry/enable-frambeuffer-ubuntu-karmic-koala-using-grub2 >> and >> http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-Logo-in-Ubuntu-10-04-140810.shtml, >> I've been able to enable the fb. >> >> The most important steps, in my opinion, could be: >> * aptitude install v86d >> * modprobe uvesafb >> >> Soon I will try compiling and running QtMoko. >> >> Cheers, >> Giacomo >> >> >>> From: EdorFaus >>> Subject: Re: [QtMoko] Error compiling on wheezy >>> >>> [...] >>> > Indeed, I miss /dev/fb0. Where can i get it? >>> >>> Hm. No framebuffer device... >>> >>> My first thought would be to check if /dev is actually bind mounted >>> properly, so that the out-of-chroot udev in (B) would take care of >>> generating /dev/fb0 for both (B) and (C). >>> >>> I see that the script used to enter the chroot tries to take care of >>> that though, so it probably is (but it wouldn't hurt to check). >>> >>> One way to check would be to see if /dev/fb0 exists on (B) even though >>> it doesn't in (C). >>> >>> Assuming that's not the problem, my next thought is to check the >>> configuration of VirtualBox, checking that it is actually set up to >>> include a graphics card that Linux can run a graphical framebuffer on. >>> >>> If it is, I think the next thing to do is to check the dmesg of (B) (if >>> the output of "dmesg" is too short, it can probably be found in >>> /var/log/messages prefixed with "kernel:"), looking for anything to do >>> with framebuffers, to see if that tells you why (B) doesn't have one. >>> >>> If that doesn't give any clues either, well... then things are a bit >>> more complex. Maybe the right driver wasn't enabled when (B)'s kernel >>> was compiled, or something. Either way, probably harder to figure out >>> than we'd like. :/ So I hope something in the above helps. >>> >>> >>>>> The same happens if I do it outside chroot (connecting with ssh -Y): >>> Just a tiny note: the -Y is probably not necessary, as it just deals >>> with forwarding X11 connections - which are not in use here. It >>> shouldn't hurt, either, though - and should certainly not cause the >>> problem you're seeing. >>> >>> Regards, >>> -Frode > -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O< ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Monday, November 26, 2012 06:08:46 PM Giacomo 'giotti' Mariani wrote: > Updates: > * I had to install libasound2 libgstreamer-plugins-base0.10-0 > libts-0.0-0 in order to solve library dependencies. > * I had no mouse in console, so I had to install gpm. Hi, are you running this on PC? You need to install then all those packages from that are in README installed with xapt. > Now I'm able to run qpe, but: > * the mouse is quite unresponsive. > * the QtMoko calibration window appears, but I'm not able to click and > calibrate it... : > Cannot open input device '/dev/tty0': Permission denied You need to be root. > readFile failed /sys/bus/platform/devices/twl4030_usb/vbus : "No such > file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/status : "No > such file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/capacity : "No > such file or directory" > readFile failed /sys/class/power_supply/bq27000-battery/current_now : > "No such file or directory" This should be fixed in git for a while. Btw the PC build is still very rough, but is quite cool for development. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Hi all. Updates: * I had to install libasound2 libgstreamer-plugins-base0.10-0 libts-0.0-0 in order to solve library dependencies. * I had no mouse in console, so I had to install gpm. Now I'm able to run qpe, but: * the mouse is quite unresponsive. * the QtMoko calibration window appears, but I'm not able to click and calibrate it... : Cannot open input device '/dev/tty0': Permission denied readFile failed /sys/bus/platform/devices/twl4030_usb/vbus : "No such file or directory" readFile failed /sys/class/power_supply/bq27000-battery/status : "No such file or directory" readFile failed /sys/class/power_supply/bq27000-battery/capacity : "No such file or directory" readFile failed /sys/class/power_supply/bq27000-battery/current_now : "No such file or directory" Any further suggestion? Thanks a lot, Giacomo On 11/23/2012 06:11 PM, Giacomo 'giotti' Mariani wrote: > Hello Frode, Everyone, > following http://ubuntuforums.org/showthread.php?t=652038 , > http://frontseed.com/entry/enable-frambeuffer-ubuntu-karmic-koala-using-grub2 > and > http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-Logo-in-Ubuntu-10-04-140810.shtml, > I've been able to enable the fb. > > The most important steps, in my opinion, could be: > * aptitude install v86d > * modprobe uvesafb > > Soon I will try compiling and running QtMoko. > > Cheers, > Giacomo > > >> From: EdorFaus >> Subject: Re: [QtMoko] Error compiling on wheezy >> >> [...] >> > Indeed, I miss /dev/fb0. Where can i get it? >> >> Hm. No framebuffer device... >> >> My first thought would be to check if /dev is actually bind mounted >> properly, so that the out-of-chroot udev in (B) would take care of >> generating /dev/fb0 for both (B) and (C). >> >> I see that the script used to enter the chroot tries to take care of >> that though, so it probably is (but it wouldn't hurt to check). >> >> One way to check would be to see if /dev/fb0 exists on (B) even though >> it doesn't in (C). >> >> Assuming that's not the problem, my next thought is to check the >> configuration of VirtualBox, checking that it is actually set up to >> include a graphics card that Linux can run a graphical framebuffer on. >> >> If it is, I think the next thing to do is to check the dmesg of (B) (if >> the output of "dmesg" is too short, it can probably be found in >> /var/log/messages prefixed with "kernel:"), looking for anything to do >> with framebuffers, to see if that tells you why (B) doesn't have one. >> >> If that doesn't give any clues either, well... then things are a bit >> more complex. Maybe the right driver wasn't enabled when (B)'s kernel >> was compiled, or something. Either way, probably harder to figure out >> than we'd like. :/ So I hope something in the above helps. >> >> >>>> The same happens if I do it outside chroot (connecting with ssh -Y): >> Just a tiny note: the -Y is probably not necessary, as it just deals >> with forwarding X11 connections - which are not in use here. It >> shouldn't hurt, either, though - and should certainly not cause the >> problem you're seeing. >> >> Regards, >> -Frode > -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O< ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Hello Frode, Everyone, following http://ubuntuforums.org/showthread.php?t=652038 , http://frontseed.com/entry/enable-frambeuffer-ubuntu-karmic-koala-using-grub2 and http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-Logo-in-Ubuntu-10-04-140810.shtml, I've been able to enable the fb. The most important steps, in my opinion, could be: * aptitude install v86d * modprobe uvesafb Soon I will try compiling and running QtMoko. Cheers, Giacomo > From: EdorFaus > Subject: Re: [QtMoko] Error compiling on wheezy > > [...] > > Indeed, I miss /dev/fb0. Where can i get it? > > Hm. No framebuffer device... > > My first thought would be to check if /dev is actually bind mounted > properly, so that the out-of-chroot udev in (B) would take care of > generating /dev/fb0 for both (B) and (C). > > I see that the script used to enter the chroot tries to take care of > that though, so it probably is (but it wouldn't hurt to check). > > One way to check would be to see if /dev/fb0 exists on (B) even though > it doesn't in (C). > > Assuming that's not the problem, my next thought is to check the > configuration of VirtualBox, checking that it is actually set up to > include a graphics card that Linux can run a graphical framebuffer on. > > If it is, I think the next thing to do is to check the dmesg of (B) (if > the output of "dmesg" is too short, it can probably be found in > /var/log/messages prefixed with "kernel:"), looking for anything to do > with framebuffers, to see if that tells you why (B) doesn't have one. > > If that doesn't give any clues either, well... then things are a bit > more complex. Maybe the right driver wasn't enabled when (B)'s kernel > was compiled, or something. Either way, probably harder to figure out > than we'd like. :/ So I hope something in the above helps. > > >> > The same happens if I do it outside chroot (connecting with ssh -Y): > Just a tiny note: the -Y is probably not necessary, as it just deals > with forwarding X11 connections - which are not in use here. It > shouldn't hurt, either, though - and should certainly not cause the > problem you're seeing. > > Regards, > -Frode -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O< ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Hi, The following contains a good bit of guesswork and assumptions, so please correct me if I'm wrong anywhere. There's also some bits which may seem obvious, but I don't know what you would find obvious and not - and besides, sometimes it's easy to miss things that are obvious in hindsight, so I figured it best to include as much as I could think of, even if you've already tried it. On 11/08/2012 04:50 PM, Giacomo 'giotti' Mariani wrote: Hello Radeck, everyone, I successfully built QtMoko in chroot on a Squeeze VirtualBox machine with target PC :-) If I understand you correctly, your setup has three major parts: (A) the host PC (actual physical PC), running some form of Linux (B) a VirtualBox virtual computer, running Debian Squeeze (C) a chroot used to build QtMoko with (C) being inside of (B), (B) running on (A), and (B) being intended solely for the purpose of building/running QtMoko, and nothing else. (Btw, that's pretty much exactly how I would do it myself - I haven't, yet, but probably will (even if only to try to scratch a few itches), so I'm glad someone's working out the kinks. ;) ) Fairly complex setup, actually, so lots of places things can go wrong. ...but now I can't run it: what do you mean by * Now switch to first console (CTRL+ALT+F1) and run it: I'm assuming that your (B) is a minimal installation, not running any graphical environment (aka X11 or X.org), just giving you a CLI console. If so, the above bit should be ignored, as it would typically make your host PC (A) switch to its console. However, if you *are* running a GUI in the virtual box, I think the easiest thing to do would be to turn it off and disable it, so it doesn't get in the way. (I don't actually think this is where you have problems, though.) 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 > Indeed, I miss /dev/fb0. Where can i get it? Hm. No framebuffer device... My first thought would be to check if /dev is actually bind mounted properly, so that the out-of-chroot udev in (B) would take care of generating /dev/fb0 for both (B) and (C). I see that the script used to enter the chroot tries to take care of that though, so it probably is (but it wouldn't hurt to check). One way to check would be to see if /dev/fb0 exists on (B) even though it doesn't in (C). Assuming that's not the problem, my next thought is to check the configuration of VirtualBox, checking that it is actually set up to include a graphics card that Linux can run a graphical framebuffer on. If it is, I think the next thing to do is to check the dmesg of (B) (if the output of "dmesg" is too short, it can probably be found in /var/log/messages prefixed with "kernel:"), looking for anything to do with framebuffers, to see if that tells you why (B) doesn't have one. If that doesn't give any clues either, well... then things are a bit more complex. Maybe the right driver wasn't enabled when (B)'s kernel was compiled, or something. Either way, probably harder to figure out than we'd like. :/ So I hope something in the above helps. The same happens if I do it outside chroot (connecting with ssh -Y): Just a tiny note: the -Y is probably not necessary, as it just deals with forwarding X11 connections - which are not in use here. It shouldn't hurt, either, though - and should certainly not cause the problem you're seeing. Regards, -Frode ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Thursday, November 08, 2012 04:50:03 PM Giacomo 'giotti' Mariani wrote: > Hello Radeck, everyone, >I successfully built QtMoko in chroot on a Squeeze VirtualBox machine > with target PC :-) Nice :) > ...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 Hmm interesting - i thought every linux has /dev/fb0. So it really does not exist? > PS I would change the README as follow: Done, thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
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@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@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 ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Sunday, November 04, 2012 02:00:32 PM Neil Jerram wrote: > Starting from efdad160239fca2e192553ee85b2da47851d3a90, I needed the > attached patch to get a successful build (exactly following the README > instructions). Hi Neil, it's applied now [1], thanks! Radek [1] https://github.com/radekp/qtmoko/commit/cbb787a61c74332e9676a0b3dc1c069d70971137 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Radek Polak writes: > i have now updated the build instructions. After many problems with wheezy as > host i have decided that the recommended way to install qtmoko is now chroot. > > It should avoid the problem with different packages/versions on the hosts - > and also the build HOWTO is a lot easier: > > https://github.com/radekp/qtmoko/blob/master/README > > I can now build the image in the chroot, but still there are some problems > when i run it on GTA04. I'll investigate what is wrong. > > You can try yourself and report if it worked. Starting from efdad160239fca2e192553ee85b2da47851d3a90, I needed the attached patch to get a successful build (exactly following the README instructions). >From 70619ca91f15f2dabfaaeaa9d941ee71674e5518 Mon Sep 17 00:00:00 2001 From: Neil Jerram Date: Sun, 4 Nov 2012 12:03:07 + Subject: [PATCH 1/9] Successful chroot building --- scripts/qtmoko-chroot.sh |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/scripts/qtmoko-chroot.sh b/scripts/qtmoko-chroot.sh index f4b812d..62d9c8f 100755 --- a/scripts/qtmoko-chroot.sh +++ b/scripts/qtmoko-chroot.sh @@ -34,7 +34,9 @@ then fi echo "Installing chroot packages" -cdebootstrap --flavour=minimal --include=build-essential,git,openssh-client,ccache,locales,procps,psmisc,libxext-dev,libasound2-dev,libdbus-1-dev,libssl-dev,libts-dev,libbluetooth-dev,libxtst-dev,libpng12-dev,libjpeg8-dev,libv4l-dev,libspeexdsp-dev,libglib2.0-dev,libsqlite3-dev,quilt squeeze ../qtmoko-chroot http://cdn.debian.net/debian/ +until cdebootstrap --flavour=minimal --include=build-essential,git,openssh-client,ccache,locales,procps,psmisc,libxext-dev,libasound2-dev,libdbus-1-dev,libssl-dev,libts-dev,libbluetooth-dev,libxtst-dev,libpng12-dev,libjpeg8-dev,libv4l-dev,libspeexdsp-dev,libglib2.0-dev,libsqlite3-dev,quilt,libgstreamer0.10-dev,libgstreamer-plugins-base0.10-dev squeeze ../qtmoko-chroot http://cdn.debian.net/debian/; do + : +done fi if [ ! -d ../qtmoko-chroot/proc/bus ] -- 1.7.10.4 After that I found that qpe.sh didn't start up at all on the phone, with messages indicating not being able to find libgstapp-0.10.so.0. Doing 'apt-get install gstreamer0.10-plugins-base' appears to have fixed that. Next, I found that the theme had reverted to Finxi, but for some reason even Finxi isn't fully installed: if I click the icon for the main menu, only the Games, Apps and Docs icons are there; the other grid positions are either empty or generic grey file icons with a ?. Then I did s/finxi/mokofaen/g in /opt/qtmoko/etc/default/Trolltech/qpe.conf, and restarted the phone. This successfully switched the theme to Mokofaen, but I still have missing icons as described above. Also I don't think it's just an icon problem, because if I click on the place where the Message icon normally is, I get an error popup saying "No application is defined for this document". Any thoughts/ideas? Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Tuesday, October 30, 2012 11:31:08 AM Giacomo 'giotti' Mariani wrote: > Hi Radek, > > > git checkout v48 > > Did not worked. > With target neo I get: > [...] > mv: cannot move `.device.vars' to > `/home/jack/qtm/build/qtopiacore/target/mkspecs/qdevice.pri': No such > file or directory Hi Giacomo, i have now updated the build instructions. After many problems with wheezy as host i have decided that the recommended way to install qtmoko is now chroot. It should avoid the problem with different packages/versions on the hosts - and also the build HOWTO is a lot easier: https://github.com/radekp/qtmoko/blob/master/README I can now build the image in the chroot, but still there are some problems when i run it on GTA04. I'll investigate what is wrong. You can try yourself and report if it worked. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
Hi Radek, > git checkout v48 Did not worked. With target neo I get: [...] mv: cannot move `.device.vars' to `/home/jack/qtm/build/qtopiacore/target/mkspecs/qdevice.pri': No such file or directory Warning: PKG_CONFIG_SYSROOT/PKG_CONFIG_SYSROOT_DIR has not been set. This means your toolchain's .pc files must contain the paths to the toolchain's libraries & headers. If configure [...] and, after creating that directory, I get: [...] -qt-gif: invalid command-line switch -qt-gfx-transformed: unknown argument -qt-mouse-tslib: unknown argument Warning: PKG_CONFIG_SYSROOT/PKG_CONFIG_SYSROOT_DIR has not been set. This means your toolchain's .pc files must contain the paths to the toolchain's libraries & headers. If configure [...] With target PC: jack@QtDebian:~/qtm/qtmoko$ cd ../build-pc/ jack@QtDebian:~/qtm/build-pc$ ../qtmoko/configure -device pc Can't enter /home/jack/qtm/qtmoko/devices/pc at /home/jack/qtm/qtmoko/src/build/bin/configure line 1614. make: *** [src/build/mkconf/configure] Error 2 jack@QtDebian:~/qtm/build-pc$ ls /home/jack/qtm/qtmoko/devices/pc ls: cannot access /home/jack/qtm/qtmoko/devices/pc: No such file or directory Thanks, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O< ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Error compiling on wheezy
On Monday 29 October 2012 17:03:21 Giacomo 'giotti' Mariani wrote: > Hello Radeck, everyone, > I'm trying to compile QtMoko v48 on a fresh virtual machine. > ... > Have you got some suggestion? I am now trying to get QtMoko working with Qt 4.8.3 and gstreamer. But it's quite hard to make it compile and working now. I can cross compile it on squeeze with emdebian toolchain and it works quite nice. I can cross compile on wheezy but then it crashes. I am now trying to make native debian package working, but it all takes a lot of time... Maybe you could try compiling older version for the start - it was much easier and it didnt involve pkg-config magic. Try git checkout v48 and compile this... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko] Error compiling on wheezy
Hello Radeck, everyone, I'm trying to compile QtMoko v48 on a fresh virtual machine. I'm following the README[1]. After pulling the git in mine $ git pull git://github.com/radekp/qtmoko.git >From git://github.com/radekp/qtmoko * branch HEAD -> FETCH_HEAD Already up-to-date. I configured (good, except for some warning) and compiled with neo target, but I had problems: [...] In file included from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Strong.h:30, from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/bindings/js/ScriptState.h:35, from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/page/Console.h:35, from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/dom/ScriptExecutionContext.h:31, from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/dom/Document.h:38, from /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/dom/Document.cpp:28: /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h: In static member function ‘static T* JSC::HandleTypes::getFromSlot(JSC::JSValue*) [with T = JSC::Structure]’: /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h:155: instantiated from ‘typename JSC::HandleTypes::ExternalType JSC::Handle::get() const [with T = JSC::Structure]’ /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/runtime/ScopeChain.h:40: instantiated from here /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h:82: warning: cast from ‘JSC::JSCell*’ to ‘JSC::Structure*’ increases required alignment of target type /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h: In static member function ‘static T* JSC::HandleTypes::getFromSlot(JSC::JSValue*) [with T = WebCore::JSDOMWrapper]’: /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Weak.h:89: instantiated from ‘typename JSC::Handle::ExternalType JSC::Weak::get() const [with T = WebCore::JSDOMWrapper]’ /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/bindings/js/ScriptWrappable.h:43: instantiated from here /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h:82: warning: cast from ‘JSC::JSCell*’ to ‘WebCore::JSDOMWrapper*’ increases required alignment of target type /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h: In static member function ‘static T* JSC::HandleTypes::getFromSlot(JSC::JSValue*) [with T = WebCore::JSDOMWindowShell]’: /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h:155: instantiated from ‘typename JSC::HandleTypes::ExternalType JSC::Handle::get() const [with T = WebCore::JSDOMWindowShell]’ /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/WebCore/bindings/js/ScriptController.h:79: instantiated from here /home/jack/qtm/qtmoko/qtopiacore/qt/src/3rdparty/webkit/Source/JavaScriptCore/heap/Handle.h:82: warning: cast from ‘JSC::JSCell*’ to ‘WebCore::JSDOMWindowShell*’ increases required alignment of target type make: *** [all] Killed With the PC target, I had more problems: jack@QtDebian:~/qtm/build-pc$ ../qtmoko/configure -device pc Running environment script for device pc with PKG_CONFIG_PREFIX= Variable PKG_CONFIG_PREFIX is now set to: /usr/lib/x86_64-linux-gnu Variable PKG_CONFIG_PATH is now set to: /usr/lib/x86_64-linux-gnu/pkgconfig Testing the system Qt: OK Qt Extended is using the following locations: Qt PREFIX = /usr Qt LIBRARIES = /usr/lib/x86_64-linux-gnu Qt BINARIES = /usr/bin Qt HEADERS = /usr/include/qt4 Qt Embedded SOURCE tree = /home/jack/qtm/qtmoko/qtopiacore/qt Qt Embedded BUILD tree = /home/jack/qtm/build-pc/qtopiacore/target Qt Extended SOURCE tree = /home/jack/qtm/qtmoko Qt Extended BUILD tree = /home/jack/qtm/build-pc Qt Extended SDK tree = /home/jack/qtm/build-pc/sdk Checking the compiler (host): OK (GCC 4, Little Endian) Checking the compiler (target): OK (GCC 4, Little Endian) Bootstrap QBuild: ... OK Testing QBuild: OK Testing for ALSA: OK Testing Media Engines: gstreamer Checking QMAKE_RPATH: Testing for OpenSSL: OK Testing for dynamic rotation: OK Testing DBUS: OK Checking for PAGE_SIZE and PAGE_MASK: MISSING WARNING: QSharedMemoryCache will not throw away unused pages Testing for strict warning flags your compiler accepts: -Wall -Woverloaded-virtual Testing for V4L2: OK Testing for prctl(): OK Testing for semtimedop: OK Testing for __malloc_hook: OK Running configure (qtopiacore)... Running environment script for device pc with PKG_CONFIG_PREFIX= Variable PKG_CONFIG_PREFIX is now set to: /usr/lib/x86_64-linux-gnu Variable PKG_CONFIG_PATH is now set to: /usr/lib/x86_64-linux-gnu/pkgconfig configure -embedded x86_64 -platform linux-g++ -xplatform /home/jack/qtm/qtmoko/devic
