[ELDK] Problems in kernel init while using busybox on ELDK 4.2

[Wolfgang Denk]

Dear Diptopal Basu,

In message <bd97640b0905290247v292802efpf823d41da54e19e0 at mail.gmail.com> you wrote:
>
>     I have tried to answer some of the questions ,

Maybe. But it seems you and me are living on different planets. I
cannot make myself understood, so I will have to give up.

> > > I linked busybox statically because I use "mklibs to generate dynamic
> > shared
> > > libs in /lib...and I wanted to remove mklibs from "possible cause of
> > error".
> >
> > I have no idea what "mklibs" might be, but you are actually
> > introducing more sources of errors here.
> 
> 
> Yes that's why in this case  I did not use mklibs and statically compiled
> the busybox . What I meant above was that since there is a possibility of
> introduction of error using mklibs I compiled the busybox statically .

Argh.  Note that you still fail to explain what "mklibs" is.

You also fail to understand that your static linking may be a source
of errors, especially when you do not test your generated binaries.

> > usually useless.
> 
> 
> I am pasting the message generated by a successful kernel boot up which was
> compiled with ELDK 4.1 . I am also attaching the cpio archive which has been
> used for this image .

You continue to answer only a fraction of the questions.  I  give  up
here. Sorry.



Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
My brother sent me a postcard the other day with this  big  sattelite
photo  of the entire earth on it. On the back it said: "Wish you were
here".                                                - Steven Wright