FreeTDS Development Group

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

> From: bizard [mailto:bizard AT propellerheads.com]
> Sent: October 15, 2002 12:48 PM
> 
> I tried the above with the latest nightly tarball (after 
> making a couple of changes to get it to compile at 
> all...documented below) and ran into the problem that 
> apparently my autoconf is not up to date enough.  It claims 
> to need 2.54 and I have 2.52.

Hold on.  Thanks very much for the report, but something doesn't make sense
to me.  You're not supposed to need autoanything to use the tarball.  You're
only supposed to need make and cc, and I guess libtool these days.
Definitely not autoconf/automake.  

If you unpack the tarball and run ./configure and get a complaint about
autoconf, we're doing something wrong.  

Was this on OS X, btw?  

> The changes I needed were line 1140 of src/tds/token.c.  make 
> complained that this was the first time info was used.  This 
> is in a section of bigendian code.  I don't know if what I 
> did was a good idea, but it compiled:)  I changed 
> &(info->current_row[curcol->column_offset]) to 
> &(current_row[curcol->column_offset]).

Thanks.  Not sure what's up with that.  

> Also, I downloaded the most recent version of src/apps/tsql.c 
> which include time.h because make complained about it.

Also noted.  

I wonder if the compile-time problems are related to the configure issues.  

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.