FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Jerry Grooms [mailto:grooms AT uky.edu]
> Sent: December 1, 2003 3:39 PM
> 
>  Frediano Ziglio <freddyz77 AT tin.it> writes:
> 
>      > Try enabling TDSDUMP... note that iconv stuff is not yet
>      > finished.  Current source is quite stable but require GNU
>      > iconv or no iconv... 
> 
> Yes, HPUX has a bundled iconv.  Are you saying that if an iconv is
> being used other than Gnu iconv that might cause problems at the
> present time?  I don't recall I specifically enabled iconv use; is
> the default to use or not to?

The default is to search for and use any installed iconv library.  To defeat
that, very recent versions support --disable-libiconv.  "./configure --help
|grep libiconv" will indicate if that's an option for yours.  As long as
you're happy with ISO-8859-1 encoding, the built-in libiconv replacement
functions will suffice.  

(Note that *any* configure script will accept and ignore spurious options.
It's considered a feature, sort of.)

> I'll look that over and try to get a TDSDUMP; maybe Michael Peppler
> can give us a hint if there's something not so obvious in the
> connection setup.

I hope it's not a bug in our ct-lib, and I wouldn't be surprised if we hear
from Michael one way or the other.  I do think TDSDUMP will make things
clearer. 

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.