[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [SOLVED] busybox sh does not run and cannot login when eabi enable d
From:       "cytan299 () netzero ! net" <cytan299 () netzero ! net>
Date:       2012-01-16 22:53:18
Message-ID: 20120116.165318.4789.0 () webmail09 ! dca ! untd ! com
[Download RAW message or body]

Hi Peter,
   I think you misunderstood what I meant by "Unbelievable". Facial expressions are \
so difficult to communicate via text :-). What I had meant was that I had spent so \
much time trying to solve this problem and it turned out to be so easy to fix. I was \
led on a wild goose chase because everything worked wit OABI enabled but failed with \
EABI enabled.

cytan

---------- Original Message ----------
From: Peter Korsgaard <jacmet@sunsite.dk>
To: "cytan299\@netzero.com" <cytan299@netzero.com>
Cc: busybox@busybox.net
Subject: Re: [SOLVED] busybox sh does not run and cannot login when eabi enable d
Date: Mon, 16 Jan 2012 10:14:13 +0100

> > > > > "cytan" == cytan299@netzero com <cytan299@netzero.com> writes:

 cytan> Unbelievable: The problem was in uClibc config. FPU must *not* be 
 cytan> Here's the uClibc config snippet:

 cytan> UCLIBC_HAS_FLOATS=y
 cytan> # UCLIBC_HAS_FPU is not set
 cytan> UCLIBC_HAS_SOFT_FLOAT=y

Why is that hard to understand? If you target doesn't have a FPU (and
you don't build your kernel with FPU emulation) things are bound to go
wrong when you configure uClibc to use one.

-- 
Bye, Peter Korsgaard


_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox


[prev in list] [next in list] [prev in thread] [next in thread]