Hi Thomas, Thomas Petazzoni wrote,

Hello,

uClibc-ng 1.0.3 causes a build failure when linking alsa-lib statically, due to __vfork() being defined in both libc.a and libpthread.a:

aserver.o: In function `pcm_shm_cmd': aserver.c:(.text+0x135a): warning: /home/peko/autobuild/instance-0/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/lib/libc.a(vfork.os): In function `__vfork': (.text+0x0): multiple definition of `__vfork' /home/peko/autobuild/instance-0/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/lib/libpthread.a(pt-vfork.os):(.text+0x0): first defined here collect2: error: ld returned 1 exit status

See more build output at:

http://autobuild.buildroot.org/results/c37/c37f8b8a27115208aa7db885d9dfdf3ad...

Look inside the toolchain, which is referenced: BR2_UCLIBC_VERSION_ARC_GIT=y

This is'nt uClibc-ng. You remember the discussion about ARC using uClibc snapshot. The ARC uclibc maintainer didn't respond on my suggestion. And Alexey asked him about his opinion without response.

With buildroot and uClibc-ng I get: file output/target/usr/bin/aserver output/target/usr/bin/aserver: ELF 32-bit LSB executable, version 1 (SYSV), statically linked, stripped

It's again something not in uClibc-master...

best regards Waldemar