FreeTDS Development Group

["Varley, David(CBorn at Alcoa)" <David.Varley AT alcoa.com.au>]

I'm happy to test where I can, I've been waiting for the current flurry of
changes to settle before getting too involved though. I seem to be chasing
package after package, I just installed openssl to try to resolve
tds_answer_challenge, but that caused more problems, one with headers and
another 3 undefined symbols (probably library paths).
[Even without --with-ssl, tds_answer_challenge is referenced from login.c]

Regarding the atoll() problem, a long is 64 bits on the alpha anyway, and
atol() returns a 64 bit int, so atoll() is not required or provided. A
simple #define atoll atol  would fix this, but I'm no autoconf guru, and
I assume that's the place for a proper fix.

David

-----Original Message-----
From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
Sent: Sunday, 4 August 2002 6:42 PM
To: TDS Development Group
Subject: [freetds] RE: convert.c and the next release


...omissis...

> 
> Apart from that, is there anyone else on the list running Tru64 who has
> been getting good results with recent CVS HEAD code ? I'm testing with
> Tru64 4.0f, and have been getting segfaults for a long time now, I've
> put it down to unstable code in CVS, or my own setup being in someway
> lacking. (The last release worked for me.)
> 

I don't think many people have a Tru64 machine to test...
Want you to become a Tru64 platform tester for FreeTDS ?

> Currently compiling with GCC 3.1.1, but I can't get a good build as yet
> due to missing atoll() and tds_answer_challenge() in the libraries,
> hopefully that's just a temporary problem ?
> 

tds_answer_challenge is a very recent problem (latest patches cause it).
For atoll problem.. thanks to post the problem.

> 
> David Varley
> C-Born Software Systems Pty Ltd
> mailto:David.Varley AT ieee.org
> 
> 

freddy77