![]() |
Xephyr / Debian/sid(64) / SDK+ / Maemo 5
Hi! Some great stuff going on here!
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: Code:
maemo-sdk list rootstraps I've successfully managed to install maemopad using Code:
sb2 -eR apt-get install maemopad osso-icons-default The I try to start the gui: Code:
maemo-sdk start gui I get no error message except for one strange one: Code:
maemo-sdk stop gui 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. |
Re: Xephyr / Debian/sid(64) / SDK+
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. Code:
Starting up runtime for fremantle5.0minimal_i386... 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. |
Re: Xephyr / Debian/sid(64) / SDK+
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] |
All times are GMT. The time now is 01:56. |
vBulletin® Version 3.8.8