On Thu, Jan 31, 2008 at 03:35:56PM +0100, Christian Kellermann wrote:
* Jorge Arellano Cid <jcid@dillo.org> [080131 13:25]:
Before this patch, we had no test for iconv. Did it work for you then? In a way yes. because my solution was to add -liconv to my LDFLAGS.
Did the new test in configure.in work? Nope it did not.
You wrote:
In a way yes. because my solution was to add -liconv to my LDFLAGS. and This breaks configure for me (OpenBSD/386 -stable). seems the test does not use the LDFLAGS=-L/usr/local/lib... My knowledge (and motivation) to fiddle with this autoconf hell is limited, so I'd kindly hand the ball over to someone else.
I assume you set LDFLAGS=-L/usr/local/lib...
but this is expected to be done by the test at configure.in:96. The test can fail though! Would you mind posting the output of:
cpp -v
in your system.
$ cpp -v Reading specs from /usr/libexec/../lib/gcc-lib/i386-unknown-openbsd4.2/3.3.5/specs Configured with: Thread model: single gcc version 3.3.5 (propolice) /usr/libexec/../lib/gcc-lib/i386-unknown-openbsd4.2/3.3.5/cc1 -E -traditional-cpp -quiet -nostdinc -v -I/usr/include -iprefix /usr/libexec/../lib/gcc-lib/i386-unknown-openbsd4.2/3.3.5/ -D__GNUC__ - #include "..." search starts here: #include <...> search starts here: /usr/include End of search list.
Hope this helps,
OK, then configure.in:96 should be adding /usr/local/lib to LDFLAGS. If I understood correctly, the missing part is "-liconv" in LIBS. The CVS has new code for this. Please test, tweak and report back. Making a blind patch with auto*tools is not easy. -- Cheers Jorge.-