[uClibc]RE: [BusyBox] Errors Compiling BusyBox: Update

[AVENARD,JEAN-YVES (HP-Australia,ex2)]

I understand that having some sort of standard in the call of main in crt0.S
would be useful.

But do we have to change it all the times. In the past 10 days, I had to
rewrite twice crt0.S, and will have to do it again if you change the way
main is called.
Sure it's fun to write ML code, but I now see that just as a waste of time.
These things should have been planified from te beginning and then we stick
to this architecture.

My $.02
Jean-Yves

> -----Original Message-----
> From: Manuel Novoa III [mailto:mnovoa3 at bellsouth.net]
> Sent: Friday, 16 February 2001 5:53 AM
> To: Erik Andersen
> Cc: uclibc at uclibc.org
> Subject: Re: [uClibc]RE: [BusyBox] Errors Compiling BusyBox: Update
> 
> 
> Erik,
> 
> On Thu, 15 Feb 2001, Erik Andersen wrote:
> > On Thu Feb 15, 2001 at 10:49:56AM -0600, Manuel Novoa III wrote:
> > > I committed the changes this morning.  busybox now builds 
> again with uClibc
> > > with the usual "make CC=gcc-uClibc-{arch}" command... at 
> least it does for i386.
> > 
> > Thanks Manuel!
> 
> Your welcome.  ;-)
> 
> Next I plan to deal with the __uClibc_main and crt0.S changes.
> 
> Also, the stdio.c code needs some work with the addition of vdprintf.
> 
> Manuel
> 
> 
> _______________________________________________
> uclibc mailing list
> uclibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc
>