Hi Zac. >> I spent a little time over the three day weekend fixing compilation on >> Open/FreeBSD. NetBSD still isn't working, it seems to be an issue with >> linking to libiconv. > > Which issue? If there is not an iconv() implementation already in the > system, the user can install GNU libiconv and it should work (in my > Ubuntu at home it worked even better with the GNU replacement, with no > 'invalid reads' notified by valgrind). > > If you give me more detail on the problem maybe I can help. > Well on all the BSD systems, I've not been able to get autotools to realize that iconv is there. This results in a ./configure resembling the following:
CFLAGS="-L/usr/local/lib -I/usr/local/include -liconv" ./configure Can you send the output of the compilation and the contents of config.log? Ya its ugly, and maybe I should be using LDFLAGS for "-L/usr/local/lib", I forget, however that above example works on both OpenBSD and FreeBSD. Even when I tell it where the iconv.h headers are, the ./configure script still says libiconv is present and thus won't link to it, and that lead to explicitly adding "-liconv". AC_CHECK_LIB should add -liconv to LDFLAGS if it is able to link with libiconv.
