[BusyBox] starting problem

Denis Vlasenko vda at port.imtp.ilyichevsk.odessa.ua
Fri Mar 26 10:34:18 UTC 2004


On Friday 26 March 2004 10:31, Ebony Zhu wrote:
> Hi,
>
> The same as me. Built a static binary couldn't help. What is the GCC and
> Glibc version did you use? I think the problem is related to GCC, not
> Glibc, since if I build Busybox with gcc2.95.3 or gcc3.2.2 with glibc
> 2.2.5, it can work. Using gcc 3.3.2 with glibc 2.2.5 can't work. Now I'm
> trying Gcc3.3.2 with glibc 2.3.2.
>
> B.R
> Ebony
>
> On Fri, 2004-03-26 at 15:49, Schwarz G., DP ITS, SEO, M wrote:
> > Hi,
> > I have the same problems like "Illegal instruction" allthough I've BB
> > already compiled static. Could You send Your makefile of BB.
> > Greetings
> > Schorsch
> >
> > > -----Original Message-----
> > > From: busybox-bounces at mail.busybox.net
> > > [mailto:busybox-bounces at mail.busybox.net] On Behalf Of Wim Vinckier
> > > Sent: Thursday, March 25, 2004 10:50 PM
> > > To: busybox at mail.codepoet.org
> > > Subject: [BusyBox] starting problem
> > >
> > >
> > > Hi,
> > >
> > > I had a few problems with my busybox and since there seems to
> > > be a lot of
> > > people out there with almost the same problems, I want to
> > > send my solution
> > > to this list.
> > > The first problem I had, was that my kernel didn't want to mount my
> > > filesystem.  My system stopped after something like "freeing kernel
> > > memory".  Before that he also gave me "freeing initrd" but my
> > > initrd was
> > > my rootfs.   I solved this problem by compiling my busybox static.
> > > After this, I couldn't run my own programs (even a simple
> > > "hello world"
> > > didn't work out).  I got errors like "Illegal instruction" and "-ash:
> > > ./hello: not found".  I've solved this by compiling it static...
> > > I wonder if someone ever could run a dynamic compiled program
> > > with the full
> > > libc library.  I need this library since I need a few other libraries
> > > which need it.

This sounds like using CPU-specific binaries on unsuitable CPU.
/sbin/init did not run because it was SIGILL'ed all the time.

What's your CPU, and for which CPU your libc compiled for?
--
vda



More information about the busybox mailing list