FreeTDS Development Group

[joseph.cygan AT philips.com]

I got it to work.  Apparently, the older 0.60 knows where to find the conf file in <installdir>/etc, but the new one needed me to set FREETDSCONF environment.  After that, it worked fine.

Sorry for the confusion.

Joe

"Lowden, James K" <LowdenJK AT bernstein.com> 2003-01-21 09:43 AM

To:        "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>         cc:        Joseph Cygan/SAT/SC/PHILIPS@AMEC         Subject:        RE: [freetds] HP-UX build issues         Classification:

From: joseph.cygan AT philips.com [mailto:joseph.cygan AT philips.com]
Sent: January 17, 2003 4:50 PM

I'm attempting to build freetds for use on HPUX 11.0 with gcc 3.0.1, gmake,
and gnu binutils.  Also with DBD::Sybase 0.95. 

When I grab the latest snapshot and try to compile it, I dont even get this
far.  Although it compiles correctly, I cannot run tsql and only get a core
dump.  

Joe, 

We went to some lengths to get FreeTDS to work correctly on HPUX 11.0, and
are getting ready to issue a new release.  I'm concerned that you "only get
a core dump" with the current snapshot when you use tsql.  Perhaps one of
the seemingly minor changes we made to it recently doesn't work as expected
on your OS.  I'm thinking specifically of the locale calls.  

Would you be willing to help track it down, so you (and other UXers) can use
the next version?  

If you set TDSDUMP, the log file should show how far tsql gets in
establishing a connection.  If it bombs out before trying to connect, that's
a clue; a backtrace would help in that case.  

If you post a log file to the list, beware it contains passwords.  

Regards, 

--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.