FreeTDS Development Group

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

> From: Jay Sauls [mailto:jaysauls AT hotmail.com]
> Sent: October 8, 2002 1:54 PM
> 
> When I tried to patch the config.c file, patch failed, looks 
> like version 
> 1.38 that was referenced in the diff of config.c isn't the 
> same version  that's in the freetds-current.tgz file.  

I think I know what's wrong, Jay.  Not why, but what.  I thought you were
using the nightly snapshot, but the date on that file is all wrong.  Does
"head ChangeLog" indicate anything since 16 September?  

Could you please try:

ftp://ftp.ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-0.60.1.tar.gz

That's the known good version.  It should work "out of the box".  

You said you're using 

ftp://ftp.ibiblio.org/pub/Linux/ALPHA/freetds/freetds-current.tgz

which should be the nightly snapshot, but it looks to me that it hasn't been
updated since 16 September.  It looks like the snapshot build isn't running
each night.  :(  From behind my company's firewall, this is what I see:

ftp> pwd
257 "/pub/Linux/ALPHA/freetds" is current directory.
ftp> ls *current*
227 Entering Passive Mode (209,191,168,20,230,183)
150 Opening ASCII mode data connection for /bin/ls.
-rw-r--r--    1 733      1002       611192 Sep 16 07:02 freetds-current.tgz

That would mean your codebase predates Steve's fixes.  

> I was considering getting all the files from CVS, but I 
> wasn't sure about 
> the stability of the tree, so I didn't.

Stability of the tree is good, just make sure you have a recent autoconf
(cf. Nick's message a few days ago).  If you're prepared to use CVS, please
do; it will save us both time.  

(I've snipped the rest of your message, but I want you to know it was very
helpful.)

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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.