On Sat, 16 Apr 2005, Eric Gillespie wrote:

> instead.  As for your libiconv change:
...

> This looks identical to lines 97 - 104.

Strange. I don't know how it got added twice. Thanks for noticing.

Anyways, my point is that I never hit that libiconv package failure
problem on my Linux systems. I wonder why others using Linux are forced to
use the libiconv package, because I never am.

I will need to look closer, maybe it is because that check is in the
.  if ${PREFER.iconv} == "native"
 ...

 Jeremy C. Reed

 	  	 	 open source, Unix, *BSD, Linux training
	  	 	 http://www.pugetsoundtechnology.com/