FreeTDS Development Group

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

> From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> Sent: September 18, 2002 1:11 PM
> 
> I think people are trying to do a binary upgrade of FreeTDS to 0.60
without
> relinking PHP against the new version.  Since it was compiled 
> and linked
> with 0.53, it's still looking for the old DBDEAD symbol from 
> the 0.53 ABI.
> We should have bumped the major library version before 0.60 
> release, so that
> people would have had an easier upgrade path (both versions 
> of FreeTDS could
> coexist until everything was recompiled and relinked).  But 
> people would
> still need to recompile to complete the upgrade in that case; 
> our current
> situation just makes it a bit more apparent that a recompile 
> is required.

The situation you describe could be some people's experience, yes.  The
original poster, Eric on 16 September, included this message:  

> /etc/httpd/modules/libphp4.so: undefined symbol: dbdead

I interpret that as a recompiled PHP not finding the new shared library.
Only by compiling PHP with 0.60 headers would PHP seek dbdead (lowercase).  

--jkl

> 
> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
> Sent: Wednesday, September 18, 2002 11:18 AM
> To: TDS Development Group
> Subject: [freetds] Re: Updating freetds 0.53 -> 0.60
> 
> 
> > problem is PHP search for function DBDEAD
> 
> Not so.  PHP is looking for the lowercase form.  Or do I 
> misunderstand?  


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.