FreeTDS Development Group

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

> From: Michael Peppler [mailto:mpeppler AT peppler.org]
> Sent: October 29, 2002 11:19 AM
> To: TDS Development Group
> Subject: [freetds] Re: sybperl 2.15 again
> 
> On Tue, 2002-10-29 at 07:56, Lowden, James K wrote:
> > > From: Steven J. Backus [mailto:backus AT math.utah.edu]
> > > Sent: October 29, 2002 10:38 AM
> > > 
> > > Today's sybperl error is:
> > > 
> > > blk_alloc not implemented on this architecture at
> > > ../blib/lib/Sybase/BLK.pm line 480.
> > 
> >         For building with FreeTDS you can now add -DNOBLK to the
> >         EXTRA_DEFS line in CONFIG.                 ^^^^^^
> > 
> > Have you done that?  It sounds like you shouldn't need bulk 
> copy support.  
> 
> Actually the error he got indicates that he did use the -DNOBLK flag.
> 
> THe problem is that the sybperl build doesn't block the Sybase::BLK
> module from being built (and tested) and as this module only uses the
> blk_*() routines... :-)

Ah, I see.  Hmm.  Is that the way you want it to be, Michael?  

I think it would be nice if we could coordinate this better.  I'd like
FreeTDS users to know when Sybperl is "as good as it gets" and what the
current limitations are.  I don't mind documenting them in our user guide.  

Maybe we could send you a patch that uses a CONFIG variable to extinguish
some errors and provide a comprehensive boiled-down list of warnings (per
your 11:33 mail).  Or do you have higher ambitions?  

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