[maemo-developers] [maemo-developers] Problems with maemo bora armel emulation

[From: Eero Tamminen]

Hi,

ext Klaus Rotter wrote:
> I have some (3) problems with my Maemo bora enviroment. I run it on a 
> 4.5. Vmware with Windows 2k as host and KUbuntu Edgy 6.10.
> 
> (1) Under SDK_ARMEL, I am not able to start the Maemo environment. There 
> is no problem if I try this with SDK_X86 eviroment.

IMHO the best development process is:
1. Develope on x86 (sbox)
2. Test, debug & fix on x86 (sbox)
3. Build an ARMEL package in armel-sbox
4. Test the package on the actual device

Debugging is *much* easier in the x86 environment.


	- Eero

> -------------------------- 8< --------------------------
> [sbox-SDK_ARMEL: ~/fractal] > af-sb-init.sh start
> Note: For remote X connections DISPLAY should contain hostname!
> Sample files present.
> Starting DBUS system bus
> Starting D-BUS session bus daemon
> Starting Maemo Launcher: maemo-launcher start failed.
> Starting Sapwood image server
> Starting Matchbox window manager
> Starting clipboard-manager
> matchbox: WARNING: failed to load /usr/share/matchbox/mbnoapp.xpm . 
> Disabling icons.
> matchbox: failed to load keyboard config
> Starting Keyboard
> sapwood-server[17915]: GLIB INFO default - server started
> Starting MAEMO AF Desktop
> [sbox-SDK_ARMEL: ~/fractal] > ls
> -------------------------- 8< --------------------------
> 
> (2) Maybe this problem has somethin to do with problem #1: I was able to
> compile & run SDL programms befor, but no I get "Inconsistency detected 
> by ld.so: rtld.c: 288: _dl_start_final: Assertion nfo->l.l_tls_modid == 
> 0' failed" running configure. I found
> http://lists.scratchbox.org/pipermail/scratchbox-devel/2006-September/000217.html 
> 
> Is this the only solution to recompile qemu-arm emulator? Maybe I should
> select another emulator? I use now:
> /scratchbox/devkits/cputransp/bin/qemu-arm-0.8.1-sb2
> Someone on maemo-irc suggested that it may be a kernel problem?
> "CONFIG_COMPAT_VDSO=y". Do I relly have to recompile my ubuntu kernel?
> 
> -------------------------- 8< --------------------------
> configure:19676: checking for SDL - version >= 1.2.8
> configure:19766: gcc -o conftest -Wall -g -O2 -I/usr/include/SDL 
> -D_REENTRANT
> conftest.c  -L/usr/lib -lSDL -lpthread >&5
> configure:19769: $? = 0
> configure:19771: ./conftest
> Inconsistency detected by ld.so: rtld.c: 288: _dl_start_final: 
> Assertion     nfo->
> l.l_tls_modid == 0' failed!
> configure:19774: $? = 127
> configure: program exited with status 127
> configure: failed program was:
> -------------------------- 8< --------------------------
> 
> 
> (3) When I start Maemo Xephyr complaints about the font path. I didn't 
> had this on my notebook (was Ubuntu 6.06 without vmware)
> 
> -------------------------- 8< --------------------------
> klaus at Touch-ubuntu:~$ . bin/start-scratchbox
> Password:error opening security policy file /usr/lib/xserver/SecurityPolicy
> Extended Input Devices not yet supported. Impelement it at line 625 in 
> ../../../../hw/kdrive/src/kinput.c
>     xkb_keycodes             { include "xfree86+aliases(qwerty)" };
>     xkb_types                { include "complete" };
>     xkb_compatibility        { include "complete" };
>     xkb_symbols              { include "pc(pc101)+us" };
>     xkb_geometry             { include "pc(pc101)" };
> Could not init font path element /usr/share/fonts/X11/TTF/, removing 
> from list!
> Could not init font path element /usr/share/fonts/X11/OTF, removing from 
> list!
> Could not init font path element /usr/share/fonts/X11/CID/, removing 
> from list!
> -------------------------- 8< --------------------------
> 
> My start-scratchbox script:
> 
> -------------------------- 8< --------------------------
> # Start Scratchbox enviroment bora
> Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac &
> sudo /scratchbox/sbin/sbox_ctl start
> /scratchbox/login
> -------------------------- 8< --------------------------
>