Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    [KDE] kde4 on os2008

    Reply
    Page 6 of 9 | Prev |   4     5   6   7     8   | Next | Last
    wolf08 | # 51 | 2008-05-02, 00:25 | Report

    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    penguinbait | # 52 | 2008-05-02, 01:54 | Report

    Originally Posted by wolf08 View Post
    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?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Gourmand | # 53 | 2008-05-02, 08:48 | Report

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

    Edit | Forward | Quote | Quick Reply | Thanks

     
    penguinbait | # 54 | 2008-05-02, 12:23 | Report

    Originally Posted by Gourmand View Post
    where did you get syscall errors? in Qt4 libs execution or compilation?
    On most KDE4 packages durring compilation

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Gourmand | # 55 | 2008-05-02, 13:02 | Report

    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...

    Edit | Forward | Quote | Quick Reply | Thanks

     
    wolf08 | # 56 | 2008-05-02, 17:46 | Report

    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Gourmand | # 57 | 2008-05-02, 18:33 | Report

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

    Edit | Forward | Quote | Quick Reply | Thanks

     
    wolf08 | # 58 | 2008-05-04, 04:22 | Report

    Originally Posted by Gourmand View Post
    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Gourmand | # 59 | 2008-05-04, 06:55 | Report

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

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

    Edit | Forward | Quote | Quick Reply | Thanks

     
    qwerty12 | # 60 | 2008-05-04, 08:08 | Report

    Originally Posted by wolf08 View Post
    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 6 of 9 | Prev |   4     5   6   7     8   | Next | Last
vBulletin® Version 3.8.8
Normal Logout