Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Feb 2006 06:50:36 +0200
From:      Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
To:        Ade Lovett <ade@FreeBSD.org>
Cc:        Craig Rodrigues <rodrigc@crodrigues.org>, freebsd-ports@freebsd.org
Subject:   Re: What broke with libtool upgrade? (devel/apr-svn)
Message-ID:  <20060228065036.0b3f2ae3@it.buh.tecnik93.com>
In-Reply-To: <DCC32FCD-C03D-4562-AACD-7E0A8FB815FA@FreeBSD.org>
References:  <20060228040930.GA52553@crodrigues.org> <DCC32FCD-C03D-4562-AACD-7E0A8FB815FA@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Feb 2006 20:29:58 -0800
Ade Lovett <ade@FreeBSD.org> wrote:

> 
> On Feb 27, 2006, at 20:09 , Craig Rodrigues wrote:
> > I'm getting bug reports (ports/93896)
> >  about devel/apr-svn and devel/apr not compiling.
> > These ports haven't been touched much recently, but
> > there seems to be something that has been triggered by some libtool
> > related work in the ports tree.  Any idea what exactly broke as a  
> > result
> > of this?  I hate debugging libtool/autoconf.
> 
> As has been somewhat extensively discussed on IRC, it appears to be  
> the second call to configure in the rather convoluted
> "run-autotools" overridden target not being correctly passed the
> '--with-apr=<X>' configure flag, or the '<X>' value being mangled, or
> otherwise broken.
> 
> The libtool related changes to this port are two-fold:
>    * adding two files to pkg-plist
>    * updating the PORTREVISION appropriately
> 
> That's it.  libtool hasn't actually gotten around to be being used
> at this point (libtool-related configure step failures are *very*  
> obvious in nature :).
> 
> It's also worth noting that pointyhat builds the package just fine:
> 
> http://pointyhat.freebsd.org/errorlogs/i386-6-latest-logs/apr-db4-1.2.2_3.log

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.

  case $CONFIG_SHELL in
  '')
    as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
do
  IFS=$as_save_IFS
  test -z "$as_dir" && as_dir=.
  for as_base in sh bash ksh sh5; do
         case $as_dir in
         /*)
           if ("$as_dir/$as_base" -c '
  as_lineno_1=$LINENO
  as_lineno_2=$LINENO
  as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
  test "x$as_lineno_1" != "x$as_lineno_2" &&
  test "x$as_lineno_3"  = "x$as_lineno_2" ') 2>/dev/null; then
             $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
             $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
             CONFIG_SHELL=$as_dir/$as_base
             export CONFIG_SHELL
             exec "$CONFIG_SHELL" "$0" ${1+"$@"}
           fi;;
         esac
       done
done
;;
  esac


-- 
IOnut - Unregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"

Ferengi Rule of Acquisition #214:
	 Never begin a negotiation on an empty stomach.
		-- ST:DS9, "The Maquis, Part I"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060228065036.0b3f2ae3>