Re: [uclibc-ng-devel] gettext 0.9.14 undefined reference to `posix_spawn_file_actions_addclose', `posix_spawnp', `posix_spawn_file_actions_adddup2', `posix_spawn_file_actions_addopen'

Hi, I'm in the process of building a mipsel feed for Optware-ng using uClibc-ng 1.0.6 and gcc-4.9.3 toolchain built using Buildroot. The first issue I stumbled upon was when I tried to build gettext 0.9.14: libtool: link: /home/alex/optware/buildroot-mipsel-ng/toolchain/ buildroot-mipsel-linux-2.6.36-uclibc-ng-4.9.3/bin/ mipsel-buildroot-linux-uclibc-gcc -std=gnu99 -g -O2 -Wl,--dynamic-linker=/opt/ lib/ld-uClibc.so.0 -Wl,-rpath -Wl,/opt/lib -Wl,-rpath-link -Wl,/home/alex/ optware/buildroot-mipsel-ng/staging/opt/lib -o .libs/msgcmp msgcmp-msgcmp.o msgcmp-msgl-fsearch.o  -L/home/alex/optware/buildroot-mipsel-ng/staging/opt/lib ./.libs/libgettextsrc.so /home/alex/optware/buildroot-mipsel-ng/builds/gettext/ gettext-tools/gnulib-lib/.libs/libgettextlib.so -lncurses /home/alex/optware/ buildroot-mipsel-ng/builds/gettext/gettext-tools/intl/.libs/libintl.so -lc -liconv -lm -Wl,-rpath -Wl,/opt/lib /home/alex/optware/buildroot-mipsel-ng/builds/gettext/gettext-tools/gnulib-lib /.libs/libgettextlib.so: undefined reference to `posix_spawn_file_actions_addclose' /home/alex/optware/buildroot-mipsel-ng/builds/gettext/gettext-tools/gnulib-lib /.libs/libgettextlib.so: undefined reference to `posix_spawnp' /home/alex/optware/buildroot-mipsel-ng/builds/gettext/gettext-tools/gnulib-lib /.libs/libgettextlib.so: undefined reference to `posix_spawn_file_actions_adddup2' /home/alex/optware/buildroot-mipsel-ng/builds/gettext/gettext-tools/gnulib-lib /.libs/libgettextlib.so: undefined reference to `posix_spawn_file_actions_addopen' collect2: error: ld returned 1 exit status The same gettext version builds fine against uclibc-0.9.33.2 with this patch: https://github.com/alllexx88/Optware-ng/blob/master/sources/gettext/ uClibc-error_print_progname.0.19.4.patch I take it, those symbols are there in the headers, but not yet implemented un uclibc-ng. I can't see from the first glance any configure switch to disable the use of those symbols, will look further into the sourcecode a bit later, maybe there's a simple workaround to not use them.