While trying to merge splashutils on a new AMD64 based gentoo system, I ran into some problems compiling klibc-1.5.15-r1 and splashutils. While klibc merged correctly after disabling ccache and bumping it to 1.5.20 (using the diff posted in bug 336830), splashutils still fails to merge while configuring libjpeg: configure:3513: checking whether we are cross compiling configure:3521: klcc -o conftest -O2 -w -ffunction-sections -fdata-sections -DWITH_ERRLIST -DTARGET_KERNEL -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER -I/var/tmp/portage/media-gfx/splashutils-1.5.4.3-r3/work/splashutils-1.5.4.3/libs/libjpeg -include /var/tmp/portage/media-gfx/splashutils-1.5.4.3-r3/work/splashutils-1.5.4.3/libs/klibc_compat.h conftest.c >&5 In file included from conftest.c:11: /usr/lib64/klibc/include/stdio.h:119: error: expected identifier or '(' before numeric constant configure:3525: $? = 1 configure:3532: ./conftest /var/tmp/portage/media-gfx/splashutils-1.5.4.3-r3/work/splashutils-1.5.4.3/libs/jpeg-8a/configure: line 3534: ./conftest: No such file or directory configure:3536: $? = 127 configure:3543: error: in `/var/tmp/portage/media-gfx/splashutils-1.5.4.3-r3/work/splashutils-1.5.4.3/libs/libjpeg': configure:3547: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. Some research showed that klibc has a dummy ferror() implementation since 1.5.17, making the "#define ferror(f) 0" macro in klibc_compat.h superfluous, see klibc GIT commit 84658b2574c373ac7b1a802e30f6f27588d0f094. I added a simple patch and added it inside a has_version clause in the ebuild. Now splashutils compiles nicely. Patch and ebuild are attached.
Created attachment 255039 [details, diff] patch for >=klibc-1.5.17 compatibility
Created attachment 255041 [details] Fixed ebuild
This should now be fixed in CVS. Thanks for reporting the problem :)
