I am sure this has been dealt with, or there is a workaround. BTW the debian arm cross-compiler package seems to have stat64 implemented, as I was able to cross compile cpio, but still I would like to compile packages natively

OK, following all the links, I end up that /usr/lib/libc.so is identical to /lib/libc.so.6. So what does the code below actally do? Simply append /usr/lib/libc_nonshared.a to libc.so.6?? Can this be done??

To honest I have never encountered anything like GROUP (..). What does it do?

OK, following all the links, I end up that /usr/lib/libc.so is identical to /lib/libc.so.6. So what does the code below actally do? Simply append /usr/lib/libc_nonshared.a to libc.so.6?? Can this be done??

To honest I have never encountered anything like GROUP (..). What does it do?

ld (linker) can be controlled by the "linker script" (see ld.info).GROUP() command instruct the ld linker to search specified libraries for unresolved symbols repeatedly until no new undefined references are created.

It's recommended that you should put the script instead of normal symbolic link from /lib/libc.so.6.

I feel like I am such an idiot. This morning, after a good nights sleep I (without even having to read your reply) completely understood what was going on. I was obsessed by the fact, that I somehow would have to concatenate a shared and a nonshared library, which seemed to be very bizarre for me.

What I did not know, and what I have leared is that a library can consist of a linker script.

Thank you for you kind explanation.

Andrew

BTW, everything works fine now, I can link and compile software like gnu cpio, gforth, etc