maemo.org - Talk
Page 6 of 9 « First 45 6 78 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   [KDE] kde4 on os2008 (https://talk.maemo.org/showthread.php?t=13958)

wolf08 2008-05-02 00:25
Re: kde4 on os2008
 
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 2008-05-02 01:54
Re: kde4 on os2008
 
Quote:
Originally Posted by wolf08 (Post 177004)
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 2008-05-02 08:48
Re: kde4 on os2008
 
where did you get syscall errors? in Qt4 libs execution or compilation?

penguinbait 2008-05-02 12:23
Re: kde4 on os2008
 
Quote:
Originally Posted by Gourmand (Post 177073)
where did you get syscall errors? in Qt4 libs execution or compilation?
On most KDE4 packages durring compilation

Gourmand 2008-05-02 13:02
Re: kde4 on os2008
 
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 2008-05-02 17:46
Re: kde4 on os2008
 
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 2008-05-02 18:33
Re: kde4 on os2008
 
Without seeing on those errors I cannot tell anything more...

wolf08 2008-05-04 04:22
Re: kde4 on os2008
 
Quote:
Originally Posted by Gourmand (Post 177257)
Without seeing on those errors I cannot tell anything more...
The "errors" are quite cryptic.

For example, here is one 'problem':

Code:
[ 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 2008-05-04 06:55
Re: kde4 on os2008
 
bad... in ported version of moc there are instruction codes and/or fucntion calls which qemu cannot execute :-(

Quote:
In other cases qemu will use 100% cpu and seems to freeze
does this happen while executing of moc?

qwerty12 2008-05-04 08:08
Re: kde4 on os2008
 
Quote:
Originally Posted by wolf08 (Post 177739)
The "errors" are quite cryptic.

For example, here is one 'problem':

Code:
[ 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.


All times are GMT. The time now is 20:53.
Page 6 of 9 « First 45 6 78 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8