Date: Sat, 10 Nov 2012 12:35:33 -0500 From: Sahil Tandon <sahil+freebsd-ports@tandon.net> To: =?utf-8?B?SsOhbiDFIGVib8Whw61r?= <sebosik@itm8.sk> Cc: ports@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: Postfix and SASL compilation problem Message-ID: <20121110173533.GD9501@magic.hamla.org> In-Reply-To: <CAK%2BpXF07XXuHWt%2B5QQ=QZ=MNOnqjb=Z2JhKUh0c4P72W6RS_Wg@mail.gmail.com> References: <CAK%2BpXF2fOASnXir71FX0mzxfEfcKaHTLfjSXZ0AJeK26cDGU=A@mail.gmail.com> <20120925015707.GA7874@magic.hamla.org> <CAK%2BpXF07XXuHWt%2B5QQ=QZ=MNOnqjb=Z2JhKUh0c4P72W6RS_Wg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2012-09-25 at 09:49:53 +0200, Ján Šebošík wrote:
> ...
> >> +++ 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?
>
> I'll test it probably today / tomorrow, and let you know later.
Can I assume this was resolved? Thanks.
--
Sahil Tandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121110173533.GD9501>