FreeTDS Development Group

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

> From: Erik Anderson [mailto:eanders AT pobox.com]
> Sent: September 18, 2002 10:08 AM
> 
> When I compile freetds-0.60 into Apache I get the following error when
> starting Apache.
> 
> [root@UNIXWORK modules]# /etc/init.d/httpd start
> Starting httpd: Syntax error on line 57 of /etc/httpd/conf/httpd.conf:
> Cannot load /etc/httpd/modules/libphp4.so into server:
> /etc/httpd/modules/libphp4.so: undefined symbol: dbdead
>                                                            [FAILED]
> 
> I have freetds-0.53 php-4.1.2, apache 1.3.20-23, and MS SQL Server 2000
> all working together but not the FreeTDS-0.60
> 
> My guess is wait for a new patch to fix the dbdead(), DBDEAD() problem.

Erik, 

I think this is a simple matter of readjusting your runtime linker.  (Bear
in mind the new default installation directories.)  

Using nm(1), you should be able to confirm that FreeTDS 0.60 exports
dbdead().  

Using ldd(1), you should be able to confirm that Apache is linked to FreeTDS
0.60.  

Could you please check those and let us know?  

All, 

Does anyone have an explanation for this?  

We have now 2 PRs for a missing dbdead() function.  That practically makes
it a FAQ.  

dbdead() -- lowercase -- is in fact exported by FreeTDS 0.60.  FreeTDS 0.53
exported DBDEAD().  
(Use nm to check.)  Apache linked to 0.60 should find dbdead().  

The only  explanation I can come up with is misconfiguration at the client.
I  think the runtime linker is finding 0.53 after Apache is recompiled with
the 0.60 header files.  

Could someone suggest how to confirm/deny my hypothesis?  How best to
determine what the runtime linker is doing?  What best to do?  

Does ldd(1) work on these systems? 

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