From owner-freebsd-questions@FreeBSD.ORG Mon Apr 2 19:51:22 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3DB4916A40F for ; Mon, 2 Apr 2007 19:51:22 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mx1.freebsd.org (Postfix) with ESMTP id 140DE13C4BA for ; Mon, 2 Apr 2007 19:51:21 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.13.8/8.13.8) with ESMTP id l32JpLEI019376 for ; Mon, 2 Apr 2007 14:51:21 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200704021951.l32JpLEI019376@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19374.1175543481.1@dc.cis.okstate.edu> Date: Mon, 02 Apr 2007 14:51:21 -0500 From: Martin McCormick Subject: php5 and SQL Scripts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2007 19:51:22 -0000 About 4 years ago, we installed php from the FreeBSD ports collection on a system in order to query a MS-SQL data base on another server. It worked fine until we upgraded to FreeBSD6.2 and php5. I had moved the old binary across and also pulled several libraries in to /usr/local/lib and the old binary seemed to be happy until we actually tried to use it at which time it hung until manually killed. After installing /usr/ports/lang/php5 and even trying /usr/ports/lang/php4, our new php gives the following error: Fatal error: Call to undefined function mssql_connect() Has anybody in the FreeBSD world seen this before and better yet, how do you fix it? We do a little piece of a back-end operation which gathers information from a web application and uses it to create or remove rules in a firewall. The folks who own the rest of the pieces of the operation are asking frequently if it is fixed yet. I am out of things to try. Obviously, something changed between our older system and the present because the object is either here but in a wrong directory or I didn't pick the right configuration options in setting up the port. The sql script has worked fine until now for all these years. Any ideas are much appreciated. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group