You are right. There related iconv strings from this log:

configure:13869: checking if iconv second argument needs const
configure:13893: x86_64-linux-gnu-gcc -c -Wall -g -fno-strict-aliasing -isystem /usr/include -U_FORTIFY_SOURCE -O2 -Wall -Werror -D_GNU_SOURCE -include ./src/include-glibc/glibc-bugs.h -I./src/include-glibc -I./src/include-glibc -I/usr/include    -I${top_srcdir}/src/racoon/missing conftest.c >&5
conftest.c: In function 'main':
conftest.c:70:3: error: passing argument 2 of 'iconv' from incompatible pointer type [-Werror]
/usr/include/iconv.h:43:15: note: expected 'char ** __restrict__' but argument is of type 'const char **'
cc1: all warnings being treated as errors
configure:13893: $? = 1

I was found same this bug unclosed in debian bugtrack system:

Did you think this problem exist on debian-based systems?

2013/3/18 Rainer Weikusat <>
Andrey Rogovsky <> writes:
> When I try compile ipsec-tools with raidlib support, configure drop me an
> error:
> checking iconv.h usability... yes
> checking iconv.h presence... yes
> checking for iconv.h... yes
> checking if iconv second argument needs const... no
> checking if -liconv is required... configure: error: cannot use iconv
> I think this a bug in configure section.

Maybe. The config.log file written by this configure-run should
contain some more details about this.

Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Ipsec-tools-devel mailing list