Date: Wed, 02 Mar 2011 19:02:25 +0100 From: Michal Varga <varga.michal@gmail.com> To: gahr@FreeBSD.org Cc: freebsd-ports@freebsd.org Subject: Re: gegl Message-ID: <1299088945.52738.69.camel@xenon> In-Reply-To: <20110302171239.GG1550@gahrfit.gahr.ch> References: <201103011706.45759.lumiwa@gmail.com> <20110302075219.GA2182@reindeer.exwg.net> <20110302100645.GB2182@reindeer.exwg.net> <4D6E5691.9060906@yandex.ru> <1299077867.52738.5.camel@xenon> <20110302152634.GF1550@gahrfit.gahr.ch> <1299080893.52738.28.camel@xenon> <20110302171239.GG1550@gahrfit.gahr.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2011-03-02 at 18:12 +0100, Pietro Cerutti wrote: > OK, I have nailed down the source of the problem. GEGL has an optional > dependency on graphics/exiv2 which is not tracked by the port, i.e. > exiv2 is not built as a dependency of the port, and GEGL doesn't rely on > it if it doesn't find it. It turns out that the failing C module > (exp_combine.c) is only compiled when EXIV is found. > > Thus, on a fresh system (i.e., tinderbox) the error won't appear. It > will, however, on a system where EXIV is installed. > Please check whether you have graphics/exiv2 installed in your system to > confirm this hypothesis. > > I have still not decided whether to include exiv2 as a mandatory or > optional dependency, cause configure doesn't handle --without-exiv2 > correctly when exiv2 is installed (i.e., GEGL will be built with EXIV > support in that case). > > Thanks for the hints, and sorry for the noise. > I see, this is pretty sneaky, there's hardly a reason for you to apologize. Yes, I do have exiv2 installed, so that would explain (as others already reported). By the way - as for the mandatory dependency (though I personally am always in favor of those - makes things unified and easier to maintain), I'd say an optional dependency would fare better with the rest of the current gegl options (optional JPEG, etc). So making exiv2 optional and patching configure to handle it properly would be the cleanest approach, I guess? I've quickly checked configure and the detection looks pretty ordinary as it is now, but atm I don't have enought time to trace it over every single step, so who knows... Might be just a case of typo somewhere in there? m. -- Michal Varga, Stonehenge (Gmail account)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1299088945.52738.69.camel>