Date: Mon, 27 Feb 2006 21:28:32 -0800 From: Ade Lovett <ade@FreeBSD.org> To: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> Cc: Craig Rodrigues <rodrigc@crodrigues.org>, freebsd-ports@freebsd.org, Ade Lovett <ade@FreeBSD.org> Subject: Re: What broke with libtool upgrade? (devel/apr-svn) Message-ID: <B6B3D504-8419-435B-9F90-2970A49ECDA8@FreeBSD.org> In-Reply-To: <20060228065036.0b3f2ae3@it.buh.tecnik93.com> References: <20060228040930.GA52553@crodrigues.org> <DCC32FCD-C03D-4562-AACD-7E0A8FB815FA@FreeBSD.org> <20060228065036.0b3f2ae3@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 27, 2006, at 20:50 , Ion-Mihai Tetcu wrote:
> Somewhere, somehow ./configure picks bash if in PATH and uses it as
> CONFIG_SHELL (I build the port by
> mv /usr/local/bin/bash /usr/local/bin/back.tmp; make); why does it
> need
> to do this when CONFIG_SHELL=/bin/sh in CONFIGURE_ENV I can't tell.
Ah hah!
Because the port Makefile target is using:
cd ${WRKDIR}/apr-${PORTVERSION}; \
${SETENV} ${SCRIPTS_ENV} ${SH} ./configure $
{CONFIGURE_ARGS}
cd ${WRKDIR}/apr-util-${PORTVERSION}; \
${SETENV} ${SCRIPTS_ENV} ${SH} \
./configure ${CONFIGURE_ARGS} ${APR_UTIL_CONF_ARGS}
Those two references to ${SCRIPTS_ENV} should be ${CONFIGURE_ENV}.
However, given that things have worked in the past, this would
suggest that there is something of a flaw in the current bash port.
Good catch.
-aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6B3D504-8419-435B-9F90-2970A49ECDA8>