Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (7)
to General by teroyk - 18 hrs, 11 mins ago - more...
|
2009-12-12
, 23:21
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Dec 2009
@ Austria
|
#2
|
To reply to my own thread:
After copying dpkg-preconfigure and linking the missing fakeroot library and installing „maemo-sdk-runtime nokia-apps nokia-binaries“ in the i386 rootstraps I get the following errors when trying to start the gui.
I haven't been able to get those sorted out but a user in #maemo confirmed them. So still no progress, unfortunately.
To me the current situation seems to be that the rootstraps are far from being usable and without owning an N900 I won't be able to develop and test for Maemo 5.
Last edited by AlexH; 2009-12-12 at 23:25.
After copying dpkg-preconfigure and linking the missing fakeroot library and installing „maemo-sdk-runtime nokia-apps nokia-binaries“ in the i386 rootstraps I get the following errors when trying to start the gui.
I haven't been able to get those sorted out but a user in #maemo confirmed them. So still no progress, unfortunately.
Code:
Starting up runtime for fremantle5.0minimal_i386... Sample files present. Starting DBUS system bus Starting D-BUS session bus daemon Starting Maemo Launcher: maemo-launchermaemo-launcher[9682]: GLIB WARNING ** Gtk - Locale not supported by C library. Using the fallback 'C' locale. . maemo-launcher: warning raising the oom shield for pid=9684 status=5632 Starting Sapwood image server Error setting value: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/apps/osso/inputmethod/have-internal-keyboard' set in a read-only source at the front of your configuration path Error setting value: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/system/osso/af/slide-open' set in a read-only source at the front of your configuration path Starting hildon-desktop maemo-invoker: error nothing to invoke Usage: maemo-invoker [options] file [file-options] Options: --delay SECS After invoking sleep for SECS seconds (default 0). --version Print program version. --help Print this help message. maemo-invoker: error nothing to invoke Usage: maemo-invoker [options] file [file-options] Options: --delay SECS After invoking sleep for SECS seconds (default 0). --version Print program version. --help Print this help message. maemo-invoker: error nothing to invoke Usage: maemo-invoker [options] file [file-options] Options: --delay SECS After invoking sleep for SECS seconds (default 0). --version Print program version. --help Print this help message. Configuring Hildon Input Method sudo: must be setuid root Starting Keyboard maemo-invoker: error nothing to invoke Usage: maemo-invoker [options] file [file-options] Options: --delay SECS After invoking sleep for SECS seconds (default 0). --version Print program version. --help Print this help message. /home/alex/.maemo-sdk/rootstraps/i386/fremantle5.0minimal_i386/usr/lib/tracker/trackerd: error while loading shared libraries: libtracker-data.so.0: cannot open shared object file: No such file or directory Starting browser daemon: browserd[9724]: GLIB WARNING ** Gtk - Locale not supported by C library. Using the fallback 'C' locale. OIL: ERROR liboiltest.c 405: oil_test_check_impl(): function mas10_u8_mmx_2 in class mas10_u8_l15 failed check (4978 > 0) || (outside=0) browserd Messages from sb2: 2009-12-13 00:13:53.369 (WARNING) maemo-launcher[9685/-147257136] SUID bit set for '/home/alex/.maemo-sdk/rootstraps/i386/fremantle5.0minimal_i386/usr/lib/maemo-launcher/defender' (SB2 may be disabled) 2009-12-13 00:13:53.501 (WARNING) bash[9709] SUID bit set for '/home/alex/.maemo-sdk/rootstraps/i386/fremantle5.0minimal_i386/usr/bin/sudo' (SB2 may be disabled) # exit 0 (0) Done mafw-dbus-wrapper[9720]: GLIB WARNING ** mafw-gst-renderer - Could not initialize hal
To me the current situation seems to be that the rootstraps are far from being usable and without owning an N900 I won't be able to develop and test for Maemo 5.
Last edited by AlexH; 2009-12-12 at 23:25.
|
|
2010-09-09
, 13:25
|
|
Posts: 22 |
Thanked: 1 time |
Joined on Jan 2010
|
#3
|
having the same problems. has anyone found a solution?
[edit: for the benefit of anyone googling this, i had these problems on a 32 bit machine, so it's not a 64-bit problem. also, scratchbox1 worked perfectly, so if you can't get scratchbox2 running, it's worth trying that]
Last edited by zem; 2010-09-11 at 21:01. Reason: pointer to workaround
[edit: for the benefit of anyone googling this, i had these problems on a 32 bit machine, so it's not a 64-bit problem. also, scratchbox1 worked perfectly, so if you can't get scratchbox2 running, it's worth trying that]
Last edited by zem; 2010-09-11 at 21:01. Reason: pointer to workaround
I've successfully managed to install and setup SDK+ in a chroot environment in my Debian/sid system running a 64 bit kernel. I'm completely new to this, so some things are a bit mysterious to me.
Info first:
I've successfully managed to install maemopad using
The I try to start the gui:
I get no error message except for one strange one:
Please give me some advice, I'm a bit lost at the moment.
Edit:
Forgot to tell you, that I can display xeyes from the chroot without problems. So I don't think that problem is related to Xephyr itself. And I've even tried with diablo4.1.2_armel rootstrap.
Edit 2:
I've now tried to use maemo-sdk in native 64 bit environment and Xephyr starts and displays everything correctly when using diablo 4.1.2.
Last edited by AlexH; 2009-12-11 at 00:03.