[maemo-developers] Qemu Error on Maemo

[From: Wei Zhou]

Little out of topic, busybox in diablo image is  1.6.1, while the latest
one is 1.11.x, does Nokia plan to upgrade this? AYK, there are many bugs
on Bugzilla shows the old busybox did not support some features (like,
`ldd', `sort -k', etc), but the latest one does. 

compare with the size

busybox 1.6.1,      223.4k
busybox 1.11.x,    763.4k

I think it's not a big problem in N810 about the size(256M/8G).

a.z

> -----Original Message-----
> From: maemo-developers-bounces at maemo.org 
> [mailto:maemo-developers-bounces at maemo.org] On Behalf Of Eero Tamminen
> Sent: Wednesday, August 13, 2008 10:31 PM
> To: ext Deepak Kr. Sharma, Noida
> Cc: maemo-developers at maemo.org
> Subject: Re: Qemu Error on Maemo
> 
> Hi,
> 
> ext Deepak Kr. Sharma, Noida wrote:
> > Thanks for your prompt reply.
> > 
> > It doesn't crash on x86. In the early stages of development 
> it used to
> > work for ARMEL, but now it doesn't.
>  >
> > So once the application has been tested for x86, the app 
> should be built
> > for ARMEL and tested on the device?
> 
> Correct.
> 
> Another difference between Scratchbox and device is that Scratchbox
> environment provides the normal GNU tools (they are required for
> building most Debian packages), but the device base system uses
> Busybox[1] instead which has some incompatibilities with the GNU tools
> (missing binaries and command line options).  This can be significant
> if your software uses shell scripts, but keeping to POSIX standard
> utilities/syntax/command line options should be (fairly) safe.
> 
> 
> There are some coding issues that could be ARM specific, but they are
> pretty rare.  Alignments are a bit different on ARM than in x86 etc,
> but these you should usually be able to catch with gcc 
> warning options,
> at least you should use "-Wall", preferably also "-Wextra".  Timings
> are also different which could trigger bugs in your code, especially
> if you're using threads.
> 
> When testing the code on x86, I would recommend using Valgrind[2]
> to check for memory access errors and leaks in your code.
> 
> 
> 	- Eero
> 
> [1] http://busybox.net/
> 
> [2] http://maemo.org/development/tools/doc/diablo/valgrind/
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>