Re: Compiling under HPUX IA64
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
2009/2/1 Michael Warchut <[email protected]>: > > > Hello > > > > I am a long time Freetds user but usually on Linux. Now I have a pair of > RX8640 servers running HPUX IA64. I am trying to get FreeTDS .84 to > compile and run under this platform but have run into copious errors from > compile errors to make check failures. Are there any special tools that > need to be installed from GNU to replace the stock HPUX set to make this > work? Any other tips? > > > > I recently got .82 to compile but when I try to connect to a SQL 2005 server > this is what I get in the error log. > > > > 13:24:18.357341 17237 (log.c:190):Starting log file for FreeTDS 0.82 > > on 2009-01-30 13:24:18 with debug flags 0xffff. > > 13:24:18.357573 17237 (iconv.c:78):Using trivial iconv > > 13:24:18.357609 17237 (iconv.c:197):names for ISO-8859-1: ISO-8859-1 > > 13:24:18.357621 17237 (iconv.c:197):names for UTF-8: UTF-8 > > 13:24:18.357633 17237 (iconv.c:197):names for UCS-2LE: UCS-2LE > > 13:24:18.357646 17237 (iconv.c:197):names for UCS-2BE: (null) > Mmmm.... I would try to install and use GNU iconv. > 13:24:18.357658 17237 (iconv.c:363):iconv to convert client-side data to the > "roman8" character set > > 13:24:18.357748 17237 (iconv.c:477):tds_iconv_info_init: use memcpy to > convert "ROMAN8"->"UCS-2LE" > > 13:24:18.357772 17237 (net.c:210):Connecting to 172.16.140.23 port 1433 (TDS > version 8.0) > > 13:24:18.358050 17237 (net.c:264):tds_open_socket: connect(2) returned > "Operation now in progress" > > 13:24:18.358133 17237 (net.c:303):tds_open_socket() succeeded > This means that port is opened > 13:24:18.358145 17237 (util.c:162):Changed query state from DEAD to IDLE > > 13:24:18.358160 17237 (login.c:735):quietly sending TDS 7+ login packet > > 13:24:18.358215 17237 (token.c:312):tds_process_login_tokens() > > 13:24:18.359100 17237 (util.c:334):tdserror(6000000000014800, > 6000000000029650, 20017, 0) > This means that mssql probably detected an invalid packet. > ... bye freddy77