From: Neil H. <nei...@ph...> - 2001-03-08 09:43:46
|
On Wed, 7 Mar 2001, Dom Lachowicz wrote: > I removed this on purpose. I wanted people to build using their system's > iconv implementation, as this would be clearly preferable to building with > our meager subset. I will try to add a configure rule - > --with-included-iconv to make us link against our included iconv. Hi Dom, I can see the merits of a push in this direction, but your "meager subset" covers all the required basic functionality for wvWare, and it appears that the system iconv implementation in many Unixes don't ... It isn't actually configure that is the problem. It seems to me that what the existing configure tests already do is the "right thing" - it evaluates the suitablity of the system iconv implementation and attempts to trigger the fallback iconv if, and only if, the system iconv implementation isn't going to work with wvWare. This seems to me to be preferable to a manually specified configure option. Also, as things stand, I don't see that the library can work at all on a host that lacks a system iconv. This seems silly when there is a working, replacement iconv available in the source tree that never gets incorporated! Regards, -- Neil Hoggarth Departmental Computer Officer <nei...@ph...> Laboratory of Physiology http://www.physiol.ox.ac.uk/~njh/ University of Oxford, UK |