Date: Tue, 25 Sep 2012 09:49:53 +0200 From: =?ISO-8859-2?B?SuFuIKllYm+57Ws=?= <sebosik@itm8.sk> To: freebsd-ports@freebsd.org Subject: Re: Postfix and SASL compilation problem Message-ID: <CAK%2BpXF07XXuHWt%2B5QQ=QZ=MNOnqjb=Z2JhKUh0c4P72W6RS_Wg@mail.gmail.com> In-Reply-To: <20120925015707.GA7874@magic.hamla.org> References: <CAK%2BpXF2fOASnXir71FX0mzxfEfcKaHTLfjSXZ0AJeK26cDGU=A@mail.gmail.com> <20120925015707.GA7874@magic.hamla.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi
I'll test it probably today / tomorrow, and let you know later.
Regards,
Jan
On Tue, Sep 25, 2012 at 3:57 AM, Sahil Tandon
<sahil+freebsd-ports@tandon.net> wrote:
> On Wed, 2012-09-12 at 12:36:47 +0200, J=E1n =A9ebo=B9=EDk 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 <sasl/sasl.h>
>>
>> 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 <sasl.h>
>> +#include <sasl/sasl.h>
>> #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
--=20
Bc. J=E1n =A9ebo=B9=EDk
technick=E9 oddelenie
ITM8 - www.itm8.sk
tel: 00421 903 469259
mail: sebosik@itm8.sk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK%2BpXF07XXuHWt%2B5QQ=QZ=MNOnqjb=Z2JhKUh0c4P72W6RS_Wg>