From owner-freebsd-ports@FreeBSD.ORG Tue Sep 25 01:57:16 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F4051065672 for ; Tue, 25 Sep 2012 01:57:16 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from cricket.hamla.org (cricket.hamla.org [206.251.255.31]) by mx1.freebsd.org (Postfix) with ESMTP id 448B18FC1A for ; Tue, 25 Sep 2012 01:57:16 +0000 (UTC) Received: from magic.hamla.org (cpe-68-174-134-215.nyc.res.rr.com [68.174.134.215]) by cricket.hamla.org (Postfix) with ESMTPSA id 5E3978A05A; Mon, 24 Sep 2012 21:57:10 -0400 (EDT) Date: Mon, 24 Sep 2012 21:57:07 -0400 From: Sahil Tandon To: sebosik@itm8.sk Message-ID: <20120925015707.GA7874@magic.hamla.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.3 at cricket.hamla.org X-Virus-Status: Clean Cc: freebsd-ports@freebsd.org Subject: Re: Postfix and SASL compilation problem X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 01:57:16 -0000 On Wed, 2012-09-12 at 12:36:47 +0200, Ján Šebošík wrote: > while I was trying to build ports/mail/postfix, the problem occured > in file ./work/postfix-2.9.4/src/global/dict_ldap.c. > > Line 232 in postfix-2.9.4/src/global/dict_ldap.c doesn't contain > proper path to sasl.h header file on FreeBSD. > Fixed line should look like this: #include > > Here is the patch: > ################### > --- dict_ldap.c.old 2012-09-11 00:39:40.000000000 +0200 > +++ dict_ldap.c 2012-09-11 00:22:56.000000000 +0200 > @@ -229,7 +229,7 @@ > /* > * SASL headers, for sasl_interact_t. Either SASL v1 or v2 should be fine. > */ > -#include > +#include > #endif Rather, the idiomatic approach is to add ${LOCALBASE}/include/sasl to the preprocessor's include path. This is done when WITH_SASL2 is defined. Does that produce undesirable results in your environment? PS: sorry for the delayed reply; I hope to be quicker in response to any follow-ups. -- Sahil Tandon