Jean-Claude Gervais wrote:
> Thank you, Pal!
> 
>       That did indeed help; by putting an empty file at
> 
> /usr/arm-softfloat-linux-uclibc/usr/include/asm/page.h
> 
> I was able to compile, however, now the link fails.
> 
> I think it might be something to do with my USE flags?
> 
> Anyone know?
> 
> [...]
> rm -f libc.a shared_libc.a
> objs=`cat obj.*` ; \
>          arm-softfloat-linux-uclibc-ar cr libc.a $objs && \
>          arm-softfloat-linux-uclibc-ar dN 2 libc.a $objs && \
>          arm-softfloat-linux-uclibc-ar dN 2 libc.a $objs
> arm-softfloat-linux-uclibc-ar cr libc.a obj.signal
> arm-softfloat-linux-uclibc-ar cr libc.a obj.string.generic
> arm-softfloat-linux-uclibc-ar cr libc.a obj.string.arm
> arm-softfloat-linux-uclibc-ar cr libc.a obj.string
> arm-softfloat-linux-uclibc-ar cr libc.a obj.sysdeps.common
> arm-softfloat-linux-uclibc-ar cr libc.a obj.sysdeps.arm
> cp libc.a shared_libc.a
> arm-softfloat-linux-uclibc-ranlib libc.a
> arm-softfloat-linux-uclibc-ld -EL -shared --warn-common --warn-once -z
> combreloc -z defs -s -z relro  -soname=libc.so.0 -o libuClibc-0.9.28.so
> \
>                 --whole-archive shared_libc.a \
>                 ../libc/misc/internals/interp.o --no-whole-archive \
>                 -init
> __uClibc_init ../lib/ld-uClibc.so.0 
> /usr/lib/gcc/arm-softfloat-linux-uclibc/4.1.2/libgcc.a 
> ../lib/ld-uClibc.so.0: warning: multiple common of `__libc_stack_end'
> shared_libc.a(__uClibc_main.o): warning: previous common is here
> arm-softfloat-linux-uclibc-ld:
> ERROR: /usr/lib/gcc/arm-softfloat-linux-uclibc/4.1.2/libgcc.a(_udivsi3.o) 
> uses VFP instructions, whereas libuClibc-0.9.28.so does not
> arm-softfloat-linux-uclibc-ld: failed to merge target specific data of
> file /usr/lib/gcc/arm-softfloat-linux-uclibc/4.1.2/libgcc.a(_udivsi3.o)
> arm-softfloat-linux-uclibc-ld:

I've had success with the following:

binutils-2.17
gcc-3.4.6-r2
linux-headers-2.6.19.2-r2
uclibc-0.9.28.3

At the least, you probably want to step down to gcc-3.4.6

hth,

Jason.
-- 
[EMAIL PROTECTED] mailing list

Reply via email to