[KDE] kde4 on os2008

[wolf08]

edit: excuse the incomprehensibility atm... I'm exhausted and going to sleep now.

I'm playing around with KDE4 in a chinook scratchbox, and I've managed to get something that at least partially runs. For example, dolphin loads but complains about invalid protocols. I think that in this case something regarding kioslaves didn't get built (or installed) correctly. I'm also currently fighting with plasma. It sometimes half-loads, but refuses to load its plasmoids (ie the taskbar). KWin4 works nicely, as well as designer-qt4 (not really kde, I know).

Once I get kde4 running well enough to give a reasonably stable interface, I'll release an image for you all to play with. Interestingly, even in this broken build, kwin/kde4 are running extremely fast, and so I don't think that there will be a problem with resources. And, as long as we don't enable opengl (in kwin, etc...) ram usage should be fairly reasonable.


One last thing. Does anyone know of any imon (inode monitor) support for the maemo kernel? And/or FAM support? Apparently it speeds up kde4 a bunch with respect to monitoring files.

[free]

Did you manage to build libqt4 with optimizations? I'm not sure if it really helps but I tried and got lost in configuring qt configuration files (what a mess..)
Most of the examples run quite fast but "chip" for example is amazingly slow.
Did you try the bittorrent client given in example? They really have crazy examples/demos.

[wolf08]

well, I did build qt4/kde4 with a mcpu optimization for the exact chip in the n8x0. I searched on google and found the relevant information on a chat log in #maemo. I honestly forgot to try any of the examples.

[wolf08]

ohh... I remember now. I decided to not make the demos to speed the compile up, remove chances of failure, and reduce the image size. Interestingly, I'm already using klipper with good results. It is fast and works off of selected text as well

[free]

well, I did build qt4/kde4 with a mcpu optimization for the exact chip in the n8x0. I searched on google and found the relevant information on a chat log in #maemo. I honestly forgot to try any of the examples.

Yes for mcpu but what's with
-mfpu=vfp -mfloat-abi=softfp

Under bora, it triggers a segfault in scratchbox's qemu.

[wolf08]

Yes for mcpu but what's with
-mfpu=vfp -mfloat-abi=softfp

Under bora, it triggers a segfault in scratchbox's qemu.

Where did you find those values? I'm pretty new to the world of optimizations, but I have heard about a qemu feature that runs the cpu from your device in your qemu session instead of emulating one. There's something about it in /scratchbox/doc/cpu-transparency.howto

Now, if you were to use the n8x0's processor to do the compile... that would take a long time... but it might get around the segfaults.

[free]

A complete rebuild takes two hours on my slow PC, I don't even dare to think about doing it on the n800.
Well, I got this value a bit from everywhere (looking at specifications, google, and mplayer build options)
Only tried on scratchbox 1 / bora. Maybe the chinook stuffs doesn't segfault.

I've put the examples/demos in a tarball, look in developper subforum. It's really worth it.

[PinCushionQueen]

So curious, how will your version of KDE be different from PenquinBait's version (other than 3.5.8 vs 4.0)? I'm currently running PenquinBait's version on my N810 and it's incredible :D I can even create shortcuts for Maemo apps to the KDE desktop.

[wolf08]

So curious, how will your version of KDE be different from PenquinBait's version (other than 3.5.8 vs 4.0)? I'm currently running PenquinBait's version on my N810 and it's incredible :D I can even create shortcuts for Maemo apps to the KDE desktop.


At the moment, his is _much_ more polished. Otherwise, there shouldn't be too much of a difference once I'm finished. I guess one important thing to note is that KDE3.5.8 is a stable well-polished relatively bug free version of KDE while KDE4 even for the desktop is unstable and buggy atm. So, It's more a project for me to play around with. (I'm running KDE4 svn on both my laptop and my desktop)

[PinCushionQueen]

At the moment, his is _much_ more polished. Otherwise, there shouldn't be too much of a difference once I'm finished. I guess one important thing to note is that KDE3.5.8 is a stable well-polished relatively bug free version of KDE while KDE4 even for the desktop is unstable and buggy atm. So, It's more a project for me to play around with. (I'm running KDE4 svn on both my laptop and my desktop)

Ah... thanks! LOL the version of KDE on my Nokia is newer than my desktop - I really should update my desktop :p So how do you like KDE4? Is Dolphin really better than Konqueror? Is it a web browser/file manager? Can you run KDE 3.x.x apps?

[wolf08]

Ah... thanks! LOL the version of KDE on my Nokia is newer than my desktop - I really should update my desktop :p So how do you like KDE4? Is Dolphin really better than Konqueror? Is it a web browser/file manager? Can you run KDE 3.x.x apps?

I love dolphin. It's really smooth, simple, and just a joy to use. However, konqueror is still my swiss army knife. I can do anything with it. So, for most simple file management tasks, I use dolphin, but for web/advanced tasks I use konqueror. And I like it that way!

I can run kde3.x.x apps by just running "/usr/bin/3xappname" if they're installed on my system. However, some of them try to use kde4 resources because of the $KDEHOME setting. So, I have a session where I "ssh -X localhost" to get back all of my normal kde3 environment variables. From there I run for example "kontact & kopete & konqueror & konversation &" and I am greeted with my kde3 apps working perfectly in my kde4 desktop!

Overall I am pleased with the state of KDE4 development. Of course, KDE 4.0.0 is not going to be for general users, and in some ways, it has not achieved even feature parity yet much less configureability parity. On the other hand, There are many things in kde4 that are simpler than their kde3 counterparts but at the same time maintain all of their configureability. For example:

Konsole - I <3 everything they changed. It's simpler to configure, looks sharper and cleaner, and is fast loading.

Kopete - Once I get support for jabber ssl (I have messed up somewhere, it does work) it will become my main messaging app. Looks clean, beautiful and seems faster. It also is easier to work with.

Amarok - This is still in pre-alpha state, but I like where it's headed. And, I already love the 1.4.x series.

Plasma - I feel like we'll really see plasma shine come kde 4.1.x. It'll make its debut in 4.0, but you can clearly see that it isn't at all finished based on what Aaron S. has been blogging about.

Step - OMFG I love this. It is a physics simulator slated for kde edu 4.1. It is fast, nice, and has simple easy to use features. You can create particles, soft bodies, rigid bodies, etc.. and can apply forces, tracers, graphers, labels. it's so nice! You should check it out when you have time.

KDE Edu - For that matter, everything in kde4edu seems polished, usable, and just better compared to kde3edu. Highlights are KAlgebra, KmPlot.

Oxygen - I had my doubts when I saw early work on the oxygen theme, but it has REALLY come far, and it puts everything else I've seen to shame. This includes Vista Areo and Mac (Aqua?). It's just beautiful. You can see some of it on the screenshot I posted above, and more at my blog ( http://blog.chatonka.com )

Wow, this really turned into a mini review of kde4. Maybe I'll have to throw it up as a blog post =).

Hope that satisfied your questions.

- And - For a status update. I'm rebuilding KDE4 for maemo4.0, this time making sure I include as many optional libraries as I can manage. Maybe I'll have better luck this time.

[wolf08]

Yes for mcpu but what's with
-mfpu=vfp -mfloat-abi=softfp

Under bora, it triggers a segfault in scratchbox's qemu.


It seems that these segfaults occur when something is compiled and then run during compilation. The segfault then happens because qemu does not replicate an armv6 (which the n800 has) correctly. The workaround for this would be to either use cpu-transparency (maybe a bash script to only use it when not running gcc?) or to disable that part of the make (which would only work if it was a check).

Hope that helps. It would be interesting to investigate the possibility of a cpu-transparency that only functioned outside of a gcc /g++ make.

[RipTorn]

From what i remember reading awhile ago wasnt kde 4.0 going to be lighter than 3.x because of the new libs or the new qt ? i would imagine its true only when heavy eye kandy isn't used.


cheers

-Rip

[free]

It seems that these segfaults occur when something is compiled and then run during compilation. The segfault then happens because qemu does not replicate an armv6 (which the n800 has) correctly. The workaround for this would be to either use cpu-transparency (maybe a bash script to only use it when not running gcc?) or to disable that part of the make (which would only work if it was a check).

Hope that helps. It would be interesting to investigate the possibility of a cpu-transparency that only functioned outside of a gcc /g++ make.
It's qmake that segfaults. Either not well built or yes, qemu doesn't like soft float point. No clue really. It's probably not worth it anyway (eventhough I would have liked to confirm..).
I tried forcing the build of qmake without these flags with a bash script awfull hack but didn't play well with scratchbox transparency.
I also tried to modify the qmake conf so that qt-tools are built without these but the libs are built with it. I failed understanding all the flags..

For me, the only thing that I'm looking for is a _packaged_ kde. Penguinbait's looks good enough but I simply don't like big archives with no uninstalls. It's like going back 10 years before. I'm a "long time" deb user, that probably explains it, it's not meant bad for people doing archives.
But I'd still be interested to see kde _4_
By the way, there is an amazing thread in 770 subforums where somebody discovered a huge (9000 packages?) armel port repository. It contains qt4.3.3 and kde 3.5.8 packages. When I get back home and play with my n800, I'll try this kde.

[gnuton]

Hi! I'm trying to package KDE4 for OS2008.
I've packaged kdelibs and kdepimlibs, (the packages are available at kblogger.garage.maemo.org), but i don't understand because if i try to run a kde4 application it segfaults! :(
For Example:

[sbox-CHINOOK_ARMEL: ~/kblogger/kblogger-kde4-1.0~alpha2/build/src] > kdeinit4
qemu: uncaught target signal 11 (Segmentation fault) - exiting
I've the same error with my executable "kblogger"! :(

kbuildsycoca4 instead hangs up!
Any suggestion is appreciated.

[wolf08]

Try running it on your tablet rather than on the scratchbox. The arm cpu emulater (qemu) doesn't have great support for actually running binaries.

[albright]

I have heard that kde4's memory footprint is significantly
smaller than 3.5.8's plus qt4 is supposed to be a lot
faster. So that would in principle be very good if
these advantages carried over to the tablet.

So please keep trying - it's just amazing to have a complete
desktop environment in your pocket!

[gnuton]

I've installed my kde4libs (~ 54 Mb with dependecies ) package (from kblogger.garaga.maemo.org) and it segfaults also on my N810. :(

[RaTm]

It would be so great to have KDE4 on the IT...
KDE 3.5.X is so slow and i think, that KDE4 will run faster.
Wouldn't it be possible to install KDE4 to the integrated 256mb flash memory!?
And/or a full replace of hildon... !?!?

[Aisu]

*bump* Any updates on KDE4s progress? I just started using it on my laptop and it's so much better and faster than 3. I have always used GNOME, but now it's completely gone ;) I'd love to know if there's some work going on.

[wolf08]

I've stopped working on it as my free time has been completely eaten up. There is a chance that I will resume my efforts with kde4.1 when I have more time later this spring or during the summer. (June at the3 latest). I am still very interested in having KDE4 on my N800 and I think that with some tweaking plasma could work very well for the environment and small screen.

Sorry if you were anxiously awaiting anything soon =/. I also am using kde4 (compiled from svn with the excellent kdesvn-build tool) and find it very comfortable and fun to work with.

[Laughing Man]

It would be so great to have KDE4 on the IT...
KDE 3.5.X is so slow and i think, that KDE4 will run faster.
Wouldn't it be possible to install KDE4 to the integrated 256mb flash memory!?
And/or a full replace of hildon... !?!?

I don't think it'd be possible to install KDE4 to the integrated 256 flash memory. To small of a space for KDE.

[Maximos]

On the subject of KDE, is there any real, complete solution for RealPlayer? Meaning, comprehensive support as in plugins, links open it when necessary, etc.

Any help with regards to do this would help immensely. Thanks alot.

[BoredOOMM]

Looks insteresting.

On the PC Desktop side, I installed KDE 4.0 - Kubuntu and it was so weak, I downgraded all except Konqueror and Amarok to gnome again.

I don't think KDE 4 was really ready to release.

Nice work on porting what you have so far though!

[migs]

Keep up the good work on the port of KDE 4 for Nokia tablets. If you can make it a simple install process like penguinbait did, you will have a huge following. Penguinbait's thread has over 45,000 views! So there is an interest for sure.

[Aisu]

Hello!

I've been trying to compile KDE 4 in Scratchbox. QT has gotten build along with all the other dependencies, but when I start on Kdelibs, I get this error after I run cmakekde (this is at the very end of the text):



-- Configuring done
make: *** No targets specified and no makefile found. Stop.


Then I try:


[sbox-CHINOOK_ARMEL: ~/kde/build/KDE/kdelibs] > make
bash: makeobj: command not found


Then point it to the scripts I downloaded:


[sbox-CHINOOK_ARMEL: ~/kde/build/KDE/kdelibs] > PATH=$PATH:/home/ty/scripts


Make again:


[sbox-CHINOOK_ARMEL: ~/kde/build/KDE/kdelibs] > make
no objdir found. Tried /home/ty/kde/build/KDE/kdelibs



I have tried this with builds from the trunk and stable, but all have given the exact same results. Is there anything special you did to compile KDE4? Any help or advice would be very much appreciated!

[wolf08]

I used kdesvn-build instead of the build scripts on techbase.kde.org. The build process kept failing for me though... seemingly on the qmake parts (which would indicate the arm emulation, because qmake runs as an arm binary). Does that help?

[Aisu]

Yes, thanks for the info! I will try that out asap.

[penguinbait]

I have been using KDE4 on Kubuntu 8.0.4 and I must say, I think I like 3.5.8 way better. Although the network connection piece is really nice, it probably won't work on the tablet anyway, not with standard maemo under the covers anyway. FYI, I am working on KDE 4.0.3 also, but don't expect anything anytime soon from me.

pb

[wolf08]

Good to see that we have a bunch of people working on it. Does anyone else have any clue why qmake is hanging for me? I have determined that it is qmake, but I can't seem to have any reliable way of making it fail other than running a cmake build for a long time.

Is there any way to specifically use an x86 qmake? Does it even make sense?

[Aisu]

I have completely given up on compiling it in scratcbox, but I've installed all the build tools on my tablet and am going to give that a try.

I kept getting the same error, even with kdesvn-build... Let's see what happens ;)

[wolf08]

Oh man, that is going to be slooooow. Good luck!

I have completely given up on compiling it in scratcbox, but I've installed all the build tools on my tablet and am going to give that a try.

I kept getting the same error, even with kdesvn-build... Let's see what happens ;)

[IcelandDreams]

Oh man, that is going to be slooooow. Good luck!

Imagine a Beowulf cluster of N8xs'

[qwerty12]

I have completely given up on compiling it in scratcbox, but I've installed all the build tools on my tablet and am going to give that a try.

I kept getting the same error, even with kdesvn-build... Let's see what happens ;)

Hehe, like wolf says, slow... :p

Is it really worth it (it's not final) ? I found kde 4 to be buggy, with 3 running better . I removed it from my ubuntu and use gnome and kde 3.*

Still if it works, we know it will work for final :)

[wolf08]

Like I said, I want to try and get a svn build working, as it's much closer to what will be 4.1. It would be interesting for a possible Google SoC project to get kde working on the tablets and a configuration for plasma that is meant for the n800's screen resolution + touchscreen.

[qwerty12]

Ah skeen, I mean no offence :)

"And/or FAM support?"
Regarding your first post, not sure if you still need it but FAM and gamin compile fine in sbox, I've got a deb on gamin if you want.

[Aisu]

Well, some news... I've gotten qt to compile and run fine, kdelibs is also compiled (several errors during make, had to use -i to even get it to proceed). But, I keep getting errors when compiling kdepimlibs "No KDE 4 Headers Found". Any ideas?

http://tablethacker.com/temporary/screenshot00.png

http://tablethacker.com/temporary/screenshot01.png

http://tablethacker.com/temporary/screenshot02.png

[qole]

I love dolphin. It's really smooth, simple, and just a joy to use. However, konqueror is still my swiss army knife. I can do anything with it. So, for most simple file management tasks, I use dolphin, but for web/advanced tasks I use konqueror. And I like it that way!

I can run kde3.x.x apps by just running "/usr/bin/3xappname" if they're installed on my system.

Heh, never occurred to me (I'm slow I guess); I've got PenguinBait's KDE debs installed, so I just ran Konqueror from the maemo terminal and hey-presto, I've got Konqueror running without having to start KDE. Of course, it takes a while to start (and close), and I have to use my bluetooth keyboard or run kvkbd, but it is a nice alternative to the brain-dead file manager app, and it's actually not bad as a browser, either.

[penguinbait]

libs and pimlibs done, working on base now

I thought it odd though, the make for the kdepimlibs completed 101%

Maybe its the love I added :)

I am occaisonally getting these errors popping up, so I am not sure if things are really going that well. Has anyone else gotten these?


qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264

It may be my core2 duo on the laptop??? Anyone?

[Aisu]

X___X How the hell did you get kdepimlibs to compile? Dear god, I have no luck... PB, I believe I will leave it in you're excessively capable hands :D

Bonus for et dei volo!

[wolf08]

Yes, I absoultely got this far. And I got the same syscall errors. I even got base to compile and install. But there seemed to be a bunch of fatal flaws (like dolphin wasn't able to find any files, konqueror wasn't able to browse anything, kdeinit was buggy and crashed) that made me wonder if some things weren't getting compiled correctly.

I think that the problem is that (and when I get home to my development environment I'll tell you more specifically) qmake runs to generate xml files and fails to do so sometimes (that's when your make is failing and hanging). It then skips that file and goes on even though it is needed for kde4 apps to work fine. These files aren't used for actually compiling kde4, meaning that the compile goes forward 'successfully', but there are missing files in the final install.

libs and pimlibs done, working on base now

I thought it odd though, the make for the kdepimlibs completed 101%

Maybe its the love I added :)

I am occaisonally getting these errors popping up, so I am not sure if things are really going that well. Has anyone else gotten these?


qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264

It may be my core2 duo on the laptop??? Anyone?

[Westy]

Please put Evolution mail on it!.... Please! Alas MS mail servers are rather ubiquitous so we should not ignore them just because we are in to linux. This is the only gripe I have with KDE on my tablet currently. If I could use evolution or something that did a similar job I would be on cloud nine bathed in happiness and my laptop could go to the bottom draw.

Looks like an ace project.

[penguinbait]

Until the scratchbox issue is resolved I do not anticipate this happening. Although ASIU compiling on his device has the best shot of it working. But compiling 50+ packages on your tablet, is going to take a while. Perhaps once QT is ported by Nokia this problem with scratchbox will get resolved??

pb

[qwerty12]

I think there is a good chance of it getting fixed :)

The qemu arm emulation is broken but hrw has managed to boot a proper emulated N800 (not the sbox rubbish). A lot of hope imo.

[Aisu]

I have given up on compiling at the moment x_x god hates me, and so does scratchbox. Don't count on anything from my end, but I may may try to make this monstrosity work later.

What do you mean emulated n800?

[penguinbait]

If anyone else is attempting this, here is a list of some of the DEPs needed. This is by far not all of them, just what I have gotten through....

I believe I am also for now giving up, maybe next version


cmake
soprano
strigi
eigen
qca
taglib qimageblitz

LibVNCServer-0.9.1.tar.gz
NetworkManager-0.6.5.tar.bz2
ORBit2-2.13.3.tar.bz2
aspell-0.60.6.tar.gz
avahi-0.6.22.tar.gz
bc-1.06.tar.gz
boost_1_35_0.tar.bz2
bzip2-1.0.5.tar.gz
clucene-core-0.9.20.tar.bz2
cyrus-sasl-2.1.22.tar.gz
decibel-0.5.0.tar.gz
dhcdbd-3.0-dbus.patch
dhcdbd-3.0.tar.bz2
enchant-1.4.1.tar.gz
fam-2.7.0.tar.gz
gdbm_1.8.3.orig.tar.gz
ggz-client-libs-0.0.14.1.tar.gz
giflib-4.1.6.tar.bz2
gnome-keyring-0.4.9.tar.bz2
gnupg-1.4.9.tar.bz2
gnupg-2.0.8.tar.bz2
gpgme-1.1.4.tar.bz2
gphoto2-2.4.1.tar.bz2
graphml_lep.zip
ilmbase-1.0.1.tar.gz
iproute2-2.6.16-060323.tar.gz
jasper-1.900.1.zip
krb5-1.6.3.tar.gz
libIDL-0.8.9.tar.bz2
libart_lgpl-2.3.20.tar.bz2
libassuan-1.0.4.tar.bz2
libbonobo-2.17.92.tar.bz2
libbonoboui-2.17.94.tar.bz2
libdaemon-0.12.tar.gz
libgcrypt-1.4.0.tar.bz2
libggz-0.0.14.1.tar.gz
libgnome-2.17.92.tar.bz2
libgnomecanvas-2.14.0.tar.bz2
libgnomeui-2.17.92.tar.bz2
libgpg-error-1.6.tar.bz2
libgphoto2-2.4.1.tar.bz2
libidn-1.8.tar.gz
libksba-1.0.3.tar.bz2
libnl-1.0-pre6.tar.bz2
libpng-1.2.26.tar.gz
libpthread-stubs-0.1.tar.bz2
libungif-4.1.4.tar.bz2
libxcb-1.1.tar.bz2
libxml2-2.6.25.tar.gz
libxslt-1.1.9.tar.bz2
mesa-common-dev_7.0.3-1_all.deb
openexr-1.6.1.tar.gz
openssl-0.9.8g.tar.gz
pcre-7.4.tar.bz2
pcre-7.6.tar.bz2
pth-2.0.7.tar.gz
soprano-2.0.1.tar.bz2
tapioca-qt-0.14.1.tar.gz
telepathy-qt-0.14.1.tar.gz
wpa_supplicant-0.5.10.tar.gz
xcb-proto-1.1.tar.bz2
xine-lib-1.1.12.tar.bz2
xscreensaver-5.05.tar.gz
zlib-1.2.3.tar.gz

[Gourmand]

Guys! You are doing great job!
I hold breath and wait for KDE4 working on my tablet. Now I play with different ported apps and feel much more like in middle of 90-th - when I first time installed SlackWare Linux. Lots of options but nothing integral. With KDE we will have several necessary applications and intagrated environment. That is whai I'd expect from Nokia. But I hope you will make it sooner.

[penguinbait]

Guys! You are doing great job!
I hold breath and wait for KDE4 working on my tablet. Now I play with different ported apps and feel much more like in middle of 90-th - when I first time installed SlackWare Linux. Lots of options but nothing integral. With KDE we will have several necessary applications and intagrated environment. That is whai I'd expect from Nokia. But I hope you will make it sooner.

I am not sure anyone is actually working on this? I Am not..

3.5.8 is way better than 4 anyway :)

[Gourmand]

3.5.8 is way better than 4 anyway

noooo.... I removed it, toooooo slooooowwwwww

and without dialogs formated for small screen it is completely useless

I tried Kubuntu with KDE4 and found it useful for small desktop computer. And I wanna have this on tablet.

[penguinbait]

noooo.... I removed it, toooooo slooooowwwwww

and without dialogs formated for small screen it is completely useless

I tried Kubuntu with KDE4 and found it useful for small desktop computer. And I wanna have this on tablet.


I am also running KDE4 on kubuntu, I think it sux, and no matter what version, trying to run on tablet with very little memory, dont expect speed. You are just waiting for disappointment.

kde 358 is very useable, just typed this... ALL dialog boxes are accessible to me. I have never found one I could not use?

[wolf08]

Honestly, I'm using kde 4.1 alpha at the moment (compiled from svn) and I'm very much liking it. And don't worry, I haven't completely given up on my efforts for the tablet =/. Just almost. Oh well.

[penguinbait]

Honestly, I'm using kde 4.1 alpha at the moment (compiled from svn) and I'm very much liking it. And don't worry, I haven't completely given up on my efforts for the tablet =/. Just almost. Oh well.

Is there a way to compile without the syscall errors in scratchbox. Until this it resolved, I think only compilation on the device would be a possibility.

am I wrong here? The bonus I suppose is now that maemo will be porting qt eventually this will have to work?

[Gourmand]

where did you get syscall errors? in Qt4 libs execution or compilation?

[penguinbait]

where did you get syscall errors? in Qt4 libs execution or compilation?

On most KDE4 packages durring compilation

[Gourmand]

what kind of errors? undefined calls? different parameters number or type?

had you close look at these errors?

system calls are C (not ++) calls
may be it's not so difficult fix it
but I have no scratchbox running yet...

[wolf08]

I think I said this earlier, but I'm pretty sure that the syscall errors are stemming from the qmake calls done during compilation of kde. Either that or some other binary getting called to make xml files on the fly.

[Gourmand]

Without seeing on those errors I cannot tell anything more...

[wolf08]

Without seeing on those errors I cannot tell anything more...

The "errors" are quite cryptic.

For example, here is one 'problem':


[ 18%] Generating toplevel_interface.cpp, toplevel_interface.h
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 18%] Generating toplevel_interface.moc
[ 19%] Generating favicon_interface.cpp, favicon_interface.h
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 19%] Generating favicon_interface.moc
[ 19%] Generating settings.h, settings.cpp
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 19%] Generating kdeinit_keditbookmarks_automoc.cpp
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
Generating bookmarkiterator.moc
Generating updater.moc
Generating bookmarkinfo.moc
Generating bookmarklistview.moc


However, in this case, the build keeps on going. In other cases qemu will use 100% cpu and seems to freeze (I've left it going for 8 hours to no avail)

What else do you want me to do to try and troubleshoot?


Oh, and for the others in the thread, I have resumed my efforts for a bit here. I'm working with kde 4.0.3 at the moment so that I can use prepackaged qt 4.3 rather than compile it myself. (I was getting errors with 4.4-rc1)

I'm through kdelibs and kdepimlibs and I'm working on kdebase now.

[Gourmand]

bad... in ported version of moc there are instruction codes and/or fucntion calls which qemu cannot execute :-(

In other cases qemu will use 100% cpu and seems to freeze

does this happen while executing of moc?

[qwerty12]

The "errors" are quite cryptic.

For example, here is one 'problem':


[ 18%] Generating toplevel_interface.cpp, toplevel_interface.h
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 18%] Generating toplevel_interface.moc
[ 19%] Generating favicon_interface.cpp, favicon_interface.h
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 19%] Generating favicon_interface.moc
[ 19%] Generating settings.h, settings.cpp
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
[ 19%] Generating kdeinit_keditbookmarks_automoc.cpp
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
qemu: Unsupported syscall: 264
Generating bookmarkiterator.moc
Generating updater.moc
Generating bookmarkinfo.moc
Generating bookmarklistview.moc
However, in this case, the build keeps on going. In other cases qemu will use 100% cpu and seems to freeze (I've left it going for 8 hours to no avail)

What else do you want me to do to try and troubleshoot?


Oh, and for the others in the thread, I have resumed my efforts for a bit here. I'm working with kde 4.0.3 at the moment so that I can use prepackaged qt 4.3 rather than compile it myself. (I was getting errors with 4.4-rc1)

I'm through kdelibs and kdepimlibs and I'm working on kdebase now.

Yes, you are right, it is broken ARM emulation.
I think Aisu has the right idea using sbrsh.

[Gourmand]

probably it could help but there is few of RAM on tablet...

[Aisu]

Oh, yeah, sbrsh is a no go x_x There is absolutely no way I've found to actually get the damn thing running for more than thirty seconds, Scratchbox and tablet refuse to speak after that. Don't count on anything from my end...

[qwerty12]

Oh, yeah, sbrsh is a no go x_x There is absolutely no way I've found to actually get the damn thing running for more than thirty seconds, Scratchbox and tablet refuse to speak after that. Don't count on anything from my end...


:(, thanks for your efforts. I'd try but ssh doesn't work wih my router. I think sbrsh uses ssh anyway.

[Aisu]

It doesn't have to go through your router, if you want. I've tried through USB networking, as well as over a wireless network. Same results...

[wolf08]

It doesn't have to go through your router, if you want. I've tried through USB networking, as well as over a wireless network. Same results...

I tried once also to get sbrsh working. Utter failure. The documentation was incomplete and seemed to be for an old version of maemo.

Are there any other solutions to cpu emulation? Or, can I set the -march or something to be of a 'lesser' arm cpu that qemu does have fully emulated?

[Gourmand]

I cannot yet beleive qemu has wrong hardware emulation...
I'd rather suppose code generation of moc or other Qt parts was wrong, may be unsupported processor code used

did you exam compiler and/or linker options in Makefile for Qt build process?

the moc compiler you use - is it the same as used in http://qt4.garage.maemo.org/ project?

[Gourmand]

I think task can be solved. Did anybody read this?

http://blog.haerwu.biz/2008/04/11/nokia-n800-emulation/

They use qemu too. If emulator had serious errors, then Maemo wouldn't work.

this could be improper code generation causing moc and other parts of KDE fail

[penguinbait]

http://bugzilla.scratchbox.org/bugzilla/show_bug.cgi?id=315


jussi.hakala@movial.fi changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |LATER




------- Additional Comments From jussi.hakala@movial.fi 2008-02-21 16:41 -------
This is a qemu problem.

A new version of cputransp devkit has been released with additional patches to
qemu 0.8.2, a (not so recent) cvs snapshot of qemu and an additional cvs
snapshot of qemu for arm architecture.

Try again with the first two and the third if your architecture is arm.

Alternatively, you can use sbrsh.

[speculatrix]

some time ago when I was cross-building qtopia2 from scratch for ARM on i386 I had these sort of problems, basically the trolltech build scripts built various utilities for ARM processor and then tried to run them on x86 processor.

the way I solved it was to build a complete i386 qt/qtopia suite from scratch, so that I had a working copy of moc, qmake etc. I then went back to the Arm build, moved the arm moc & qmake binaries aside, then copied over the i386 binaries. I changed the ownership and made the files read only, so that the build process couldn't trample over them.

it worked OK for me, although I did have to do some funky environment setting to make it all work, but that's almost certainly less of a problem with qt4 now.

[wolf08]

I'm confused. Is there any way for us to test this now?

scratchbox seems like a pretty fragile build to me and I'm worried about mucking around in the qemu emulation.

http://bugzilla.scratchbox.org/bugzilla/show_bug.cgi?id=315


jussi.hakala@movial.fi changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |LATER




------- Additional Comments From jussi.hakala@movial.fi 2008-02-21 16:41 -------
This is a qemu problem.

A new version of cputransp devkit has been released with additional patches to
qemu 0.8.2, a (not so recent) cvs snapshot of qemu and an additional cvs
snapshot of qemu for arm architecture.

Try again with the first two and the third if your architecture is arm.

Alternatively, you can use sbrsh.

[penguinbait]

I'm confused. Is there any way for us to test this now?

scratchbox seems like a pretty fragile build to me and I'm worried about mucking around in the qemu emulation.


I filed the bug a while ago, to be honest, I am not sure if the build for maemo uses the latest parts. It may be as simple as upgrading scratchbox?

[Gourmand]

moc is a kinda of macroprocessor, it is system independed

if the problem persists only with moc - then we can use i386 moc to convert .h to .cpp files

looks like speculatrix talking about similar way...

[penguinbait]

Well, I was thinking?? Duh QT gives me the same syscall errors when compiling, thats why I never could do this before. Anyway, this has to have been solved to compile QT, so what did they do?

[wolf08]

It looks like scratchbox2 has released a version that actually plays nicely with sbrsh, so I'm going to play around with that. I've already got usb networking and sbrsh installed and working, quick and easy with these links:

https://garage.maemo.org/frs/download.php/3817/install.html
http://maemo-sdk.garage.maemo.org/sbrsh-sshfs.html

Hopefully this will help.

[Gourmand]

oh, yea... :-))

[qwerty12]

Here's summat else, in our n800's, the arch is armv6l. Qemu in sb1 emulates a armv5l. Odd.

[Gourmand]

what about sb2?

[qwerty12]

Never tried it. I don't like sb2. Also when sb1 is installed, I can't install sb2 on my system at the same time.

[Gourmand]

is any advance with kde4 using sb2?

or ALL are playing with preDiablo?

[wolf08]

Isn't sb2 still with chinook? I'm using it currently, but I've taken yet another break from my kde4 trials.

[wolf08]

Isn't sb2 still with chinook? I'm using it currently, but I've taken yet another break from my kde4 trials.

[wolf08]

Hmm, everything seems to come full circle. With the update of the prepackaged qt4 libs to 4.4 I've decided to have another go at this, with the intent of actually creating patches for the things I fix. And, amazingly, I got sbrsh working. Maybe I need to post a guide for that....

Anyways, here goes kdelibs. No "unsupported syscall" messages, which makes me happy =).

[Aisu]

Hmm, everything seems to come full circle. With the update of the prepackaged qt4 libs to 4.4 I've decided to have another go at this, with the intent of actually creating patches for the things I fix. And, amazingly, I got sbrsh working. Maybe I need to post a guide for that....

Anyways, here goes kdelibs. No "unsupported syscall" messages, which makes me happy =).

For god's sake, man, post that tutorial! :D

[qwerty12]

I've patched my sbox1's arm emulation to fix unsupported **** and installed new compilers (2008 compared to 2005) but wolf's done it with sbrsh, hope it gets released soon :)

[wolf08]

Alright, I'll see what I can do. I had the hardest time setting it up... (this was like my fourth try since Nov 2007) and it would be nice to have a decent guide.

[wolf08]

Well, kdelibs is still compiling, slowly. (very slowly, I'm 10% done).

And, in other news, I have a draft of a guide for setting up sbrsh. I may be assuming more than I have mentioned at the top. Please leave a comment if there are any issues with the guide.

http://blog.chatonka.com/2008/05/using-cpu-transparency-with-scratchbox/

[wolf08]

Well, I went back to qemu-arm-cvs-m for a sec to get around some weird compile error in kjsembed. When it moved on to solid/solid I get these:

[ 27%] Generating org_kde_solid_networking_client.cpp, org_kde_solid_networking_client.h
qemu: uncaught target signal 4 (Illegal instruction) - exiting

I'm back to sbrsh, but that's a new one.....

qwerty12, how did you patch your qemu? Any chance you could share that with me?

[svs57]

Do anybody know how to fix klipper in status bar?
I start klipper. It'a appear in status bar. If I make a changes in status configuration klipper disappear :(. It's running but not in status bar.