devel/apr-svn (apr-db4-1.2.2_2) (configure error)

[Bill Milford]

> From: owner-freebsd-ports at freebsd.org [mailto:owner-freebsd-ports at freebsd.org] On Behalf Of Boris
> Samorodov
> Sent: Monday, February 27, 2006 11:38 AM
> To: Adi Pircalabu
> Cc: Carsten Schütze; freebsd-ports at freebsd.org
> Subject: Re: devel/apr-svn (apr-db4-1.2.2_2) (configure error)

> On Mon, 27 Feb 2006 13:11:22 +0200 Adi Pircalabu wrote:
> > On Sat, 25 Feb 2006 09:39:24 +0100
> > Carsten Schütze <schuetze.carsten at gmx.de> wrote:

> > > > I've reported this to ade at FreeBSD.org as (s)he did the mega-commit
> > > > on libtool, which is
> > > > When this broke for me.

> > > I had to build wednesday 260 of 590 ports again with libtools built
> > > without problems.
> > > Or is devel/apr-svn an exception? I can't build last 5 ports with
> > > portupgrade -a.

> > Hi, did you manage to update it in the meantime? Cause I've just filed
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=93896

> Hm, weird. I've got this situation at one of my testing machines. It
> is 6.1-PRERELEASE i386. Ktrace of configure showed that somehow bash
> was used instead of sh. After deletting bash all goes normally. But I
> can't reproduce it on other i386/amd64 6.0/6.1-PRERELEASE mashines...


> WBR
-- 

I am seeing this on my FreeBSD 6.1 box.
Uname:  FreeBSD mail2.milfordmail.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #7: Mon Feb 27 14:24:07
CST 2006     root at mail2.milfordmail.com:/usr/obj/usr/src/sys/GENERIC  i386

I actually started seeing it the day before the libtools update hit.  I think it was the perl5.8.8
update that may have triggered it.

I have been noticing that all configure scripts are having errors.  They are not acting on any
arguments.

I get this error message at the beginning of any configure script: 
      configure: WARNING: you should use --build, --host, --target

I am trying to install OpenCA which is not in the ports tree, but it configure file does the same
thing.  I too have verified that for some reason bash is getting called and if I rename the bash
executable in /usr/local/bin it functions correctly.

./configure --help doesn't even work.

I think this will cause major problems in building any port that required arguments to configure.

I am relatively new to this mailing list so forgive any omissions and please ask for what ever
information will help solve this.

Bill Milford