Denys Vlasenko wrote: > On Thursday 22 November 2007 01:14, saravanan chanemouganandam wrote: >> Hi, >> >> The rootfs "root_fs_arm.ext2.bz2" which I am testing was downloaded from >> the reference link >> http://dslinux.gits.kiev.ua/trunk/uClibc/docs/uclibc.org/toolchains.html. >> As I have some problem with toochain, I have started to test first using >> the existing rootfs built for arm the target which failed to work. >> >> Test with (init=/sbin/hello) "Hello world" statically linked using uclibc >> doesn't show any message whereas statically linked using glibc shows the >> message. I wonder why it doesn't work well with uclibc. Is this problem >> due to the kernel-headers or uclibc config ? > > Also may be bad choice of ARM processor flavor, and uclibc code > ended up containing commands which are not supported by your processor. > > This is a quite typical cause of "my init doesn't run!" problem. >
The following questions are the classical: where are we/you going? The bug track system is feed with all the bugs or reading this ml is the only way to be acknowledged about each bug discovery? Is there some kind of bug report sum which can help me to choose a stable version of busybox in order to go in production? I am seeing bugs in well known application like cut or tar, are there before and nobody discover or they came out because the bb new era? In the last case is there any plan to stabilize bb? Thanks, Roberto _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
