Mike,

Thanks for taking the time to reply.  Yeah, I know the version is old.  We
have a telecom embedded system we inherited and there is a lot of code and
too few worker-bees.  We are constrained by 2.4.9 kernel, which in turn
dictates what versions of GCC/GLIBC are usable for a PowerPC-603e target.
Per Dan Kegel's crosstools site, there is no encouraging news here, seems
like we are stuck with old compilers/lib unless we upgrade to 2.6.x kernel
(too many driver-level changes, and therefore person-months of testing, for
this to be viable for us at this time).  Reality puts a damper on things :-(

If anybody has a config for a later 2.4.x kernel that works with a newer
GCC/GLIBC on a ppc-603e, I'd love to hear about it and get some help
building it.

Shash

On 5/24/07, Mike Frysinger <[EMAIL PROTECTED]> wrote:

On Thursday 24 May 2007, Sasvata Chatterjee wrote:
> gcc-2.95-3

generally this version is too old to be worth the time ...

> 1) ULLONG_MAX not defined (which I fixed by #define ULLONG_MAX
> ULONG_LONG_MAX in include/libbb.h).  Similar for LLONG_MAX and
LLONG_MIN.

this is usually because your cross-compiler is broken ... if '#include
<limits.h>' does not define those things, go fix your cross-compiler

> 2) Needed to take out -static-libgcc from Makefile.flags to avoid
> compile-time warnings for gcc

gcc-2.x is too old, upgrade

> 3) A warning on the union inside len_and_sockaddr structure:
> include/libbb.h:304: warning: unnamed struct/union that defines no
> instances

gcc-2.x is too old, upgrade

> 4) The biggie, cannot compile libbb/xatonum.c:
>  CC      libbb/xatonum.o
>   powerpc-603e-linux-gnu-gcc: unrecognized option `-static-libgcc'
>   In file included from libbb/xatonum.c:21:
>   libbb/xatonum_template.c:88: macro `xstrtou' used with too many (2)
args
>   libbb/xatonum_template.c:114: macro `xatou' used without args
>   libbb/xatonum_template.c:172: macro `xato' used without args

gcc-2.x is too old, upgrade
-mike


_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox

Reply via email to