[BusyBox] [Busy box] can't resolve symbol.

[Cedric Aubert]

Yes I am agree with you, float support in the libc
is better than kernel emulation for performance. :-)

But it's work too ! :-) It's just a solution.

But I use libc support for float today, I just notice
this solution.

> -----Original Message-----
> From: Leibowitz, Mike
[mailto:mike.leibowitz at cirrus.com]
> Sent: Tuesday, June 24, 2003 3:28 PM
> To: 'cedric_aubert at yahoo.fr'; BusyBox; Hiroaki Ibe
> Subject: RE: [BusyBox] [Busy box] can't resolve
symbol.
> 
> 
> You will get a performance penalty for doing this,
instead of
> having libc haveing softfloat.  Every time the libc
does a
> floating point operation, it will context switch to
kernel mode
> to handle the emulation.
> 
> > -----Original Message-----
> > From: Cedric Aubert
[mailto:cedric_aubert at yahoo.fr]
> > Sent: Tuesday, June 24, 2003 6:09 AM
> > To: BusyBox; Hiroaki Ibe
> > Subject: RE: [BusyBox] [Busy box] can't resolve
symbol.
> > 
> > 
> > Hi
> > 
> > I had the same problem but the answer that erik
give
> > to me wasn't the
> > solution of my problem. If I remenber what I did,
it
> > was my configuration
> > that was wrong.
> > 
> > I use MPC860 that don't have float program unit
(FPU)
> > and I don't compile
> > Uclibc with float support and don't compile my
kernel
> > with the FPU emulation
> > so I had not float support.
> > 
> > To work I had to compile kernel with FPU emulation
so
> > uclibc (without float
> > option)
> > let kernel work (by the emulation) for float
> > operation. You can also
> > compile kernel without FPU emulation but you had
to
> > compile uclibc with the
> > float option.
> > 
> > Expect that help.
> > 
> > Cedric
> > 
> > > -----Original Message-----
> > > From: busybox-bounces at busybox.net
> > [mailto:busybox-bounces at busybox.net]On
> > > Behalf Of Hiroaki Ibe
> > > Sent: Tuesday, June 24, 2003 12:19 PM
> > > To: busybox at busybox.net
> > > Subject: [BusyBox] [Busy box] can't resolve
symbol.
> > >
> > >
> > > Hi all,
> > >
> > > I am finally succesfully build BusyBox with a
> > powerpc gcc
> > > cross compiler build with uclibc  (Thanks Erik
:-)
> > >
> > > But I have some trouble when using some command
like
> > > ls, mount or other
> > >
> > > # ls
> > > ls: can't resolve symbol '__eqdf2'
> > > ls: can't resolve symbol '__floatsidf'
> > > ls: can't resolve symbol '__ltdf2'
> > > ls: can't resolve symbol '__adddf3'
> > > ls: can't resolve symbol '__fixdfsi'
> > > ls: can't resolve symbol '__negdf2'
> > > ls: can't resolve symbol '__divdf3'
> > > ls: can't resolve symbol '__muldf3'
> > > ls: can't resolve symbol '__truncdfsf2'
> > > ls: can't resolve symbol '__nedf2'
> > > ls: can't resolve symbol '__gedf2'
> > > ls: can't resolve symbol '__subdf3'
> > > bin         dev         proc        usr
> > > boot        etc         linuxrc     sbin
> > > #
> > >
> > > I read a similar problem in busybox ML.
> > > In the tread "[Busy Box] Busy box runtime :can't
> > resolve symbol."
> > > Eric answered as below
> > >
> > > "These are part of libgcc.  With newer gcc
versions,
> > rather than
> > > staricly linking libgcc into each application,
> > libgcc is now a
> > > shared library, /lib/libgcc_s.so.1, which it
looks
> > like you
> > > failed to install into your root filesystem."
> > >
> > > So I installed /lib/libgcc_s.so.1 manually, but
The
> > problem does
> > > not be resolved.
> > >
> > > I think this problem is due to .config of
uClibc.
> > >
> > > so I tried to enable "Add unresolved libgcc
symbols
> > to uClibc" in
> > > "make menuconfig" of uClibc.
> > > then I remaked uClibc & buxybox(with the
compiler
> > wrapper built
> > > by uClibc).
> > > then I installed /lib/libgcc_s.so.1 manually.
> > >
> > > It cause new problem!!
> > > When I boot my linux, It stop at below.
> > >
> > > Freeing unused kernel memory :56k init
> > > init: can't resolve symbol '__eqdf2'
> > > init: can't resolve symbol '__floatsidf'
> > > init: can't resolve symbol '__ltdf2'
> > > init: can't resolve symbol '__adddf3'
> > > init: can't resolve symbol '__fixdfsi'
> > > init: can't resolve symbol '__negdf2'
> > > init: can't resolve symbol '__divdf3'
> > > init: can't resolve symbol '__muldf3'
> > > init: can't resolve symbol '__truncdfsf2'
> > > init: can't resolve symbol '__nedf2'
> > > init: can't resolve symbol '__gedf2'
> > > init: can't resolve symbol '__subdf3'
> > >
> > > I don't know what to do next.
> > > please help me!!
> > >
> > >
> > >
> > > ----
> > > Hiroaki Ibe
> > > Waseda uni.
> > > Information & conputer science
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > busybox mailing list
> > > busybox at busybox.net
> > > http://busybox.net/mailman/listinfo/busybox
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > SBC Yahoo! DSL - Now only $29.95 per month!
> > http://sbc.yahoo.com
> > _______________________________________________
> > busybox mailing list
> > busybox at busybox.net
> > http://busybox.net/mailman/listinfo/busybox
> > 

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com