From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Apr 13 08:34:36 2011 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A347106566B for ; Wed, 13 Apr 2011 08:34:36 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0F4AD8FC12 for ; Wed, 13 Apr 2011 08:34:35 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.3) with ESMTP id p3D8GL6B036943 for ; Wed, 13 Apr 2011 11:16:22 +0300 (EEST) (envelope-from mamalos@eng.auth.gr) Message-ID: <4DA55BC6.6090704@eng.auth.gr> Date: Wed, 13 Apr 2011 11:16:06 +0300 From: George Mamalakis User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110109 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-ports-bugs@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: php ldap_sasl_bind not available for FreeBSD? X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2011 08:34:36 -0000 Dear all, We are writing a php script that has to use sasl/gssapi authentication with openldap. When I saw the available options of lang/php5, lang/php5-extensions and net/php5-ldap I realized that there was no option regarding sasl-ldap support. When I used the function ldap_sasl_bind() to connect to my openldap server, php returned the error: "Call to undefined function ldap_sasl_bind()". In order to build php with ldap_sasl support, I had to do what http://php.net/manual/en/function.ldap-sasl-bind.php suggested, which was to alter /usr/ports/lang/php5/Makefile to include /--with-ldap-sasl /in its//configuration options. After that everything worked as expected, but I suspect that there should be a FreeBSD-ports-centric way to achieve this. Should I send a PR to the port maintainer, or is there something I am missing regarding this issue? Thank you all for your time in advance, mamalos // -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379