Date: Fri, 26 Aug 2011 07:35:20 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= <decke@bluelife.at> To: Warren Block <wblock@wonkity.com>, Rusty Nejdl <rnejdl@ringofsaturn.com> Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox on FreeBSD 8.2 Message-ID: <1314336920.4027.5.camel@Nokia-N900-42-11> In-Reply-To: <alpine.BSF.2.00.1108251904050.7028@wonkity.com> References: <201108252055.p7PKtI3J001414@mail.wynn.com> <assp.021810285c.2144761c39a0590435faf8a1c6a57cef@ringofsaturn.com> <alpine.BSF.2.00.1108251904050.7028@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fr., 26. Aug. 2011 03:06:41 CEST, Warren Block <wblock@wonkity.com> wrote:
> On Thu, 25 Aug 2011, Rusty Nejdl wrote:
>
> > I was building a port that depended on threaded perl and used code
> > like this:
> >
> > .if exists(${PERL})
> > PERL_THREADS!= ${PERL} -V::usethreads
> > .if ${PERL_THREADS}!="'define';"
> > IGNORE= needs a threaded Perl, build with WITH_THREADS=yes
> > flag and try again
> > .endif
> > .else
> > IGNORE= needs an existing installation of Perl built with
> > WITH_THREADS=yes
> > .endif
> >
> > Perhaps you could use something similar?
>
> Some searching found security/clamav/Makefile:
>
> .if (defined(WITH_LLVM) || defined(WITH_LLVM_PORTS)) &&
> defined(WITH_TESTS) pre-configure:
> @if ! ${PYTHON_CMD} -c "import thread" >/dev/null 2>&1; then \
> ${ECHO_MSG} ""; \
> ${ECHO_MSG}
> "=========================================================================
> ${ECHO_MSG} "= Unit tests REQUIRES python built with
> thread support, and yours is not. ${ECHO_MSG} "= It will
> not be called during this build ${ECHO_MSG}
> "=========================================================================
> ${ECHO_MSG} ""; \ ${TOUCH}
> ${PY_NO_THREAD}; \ fi .endif
I know that a few ports try to be smart and check a bit more then others but the problem is that checking for each and every combination of options for all dependencies does not scale. In big ports you end up with a big mess. Many projects have their configure to check specific features and version ranges of their requirements which usually gives you a good idea of what is wrong but vbox doesnt. So if someone wants to improve that send a patch for vbox configure to check for python threads.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1314336920.4027.5.camel>