Message-Id: <200001272130.QAA12899@delorie.com>
From: "Mark E." <snowball3 AT bigfoot DOT com>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Thu, 27 Jan 2000 16:36:07 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: bash203s.zip updated
References: <200001262042 DOT PAA12634 AT delorie DOT com>
In-reply-to: <Pine.SUN.3.91.1000127091132.15566A-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12a)
Reply-To: djgpp-workers AT delorie DOT com

> 
> On Wed, 26 Jan 2000, Mark E. wrote:
> 
> > configure.in sets it using this method:
> > BUILD_DIR=`pwd`
> > AC_SUBST(BUILD_DIR)
> 
> This is highly non-standard; no other GNU package does this.
> 
> Can you override this from the environment?  Or perhaps the configure
> script has some command-line option to do that?

No and no.

> 
> suggest to look for any reasonable way to avoid forcing the users into
> running configure.
> 
> One way would be to modify configure.in and regenerate the configure
> script.

Yes, but I don't see what could be done to fix it.

> I would even consider editing Makefile's to change the value
> of BUILD_DIR before packaging, if no other trick solves this.
> 

Right now, this the only method I think will work. I could just warn that if 
they re-run configure, the generated files will be site specific. And then 
ask the Bash maintainer to please have 2.04 follow the standard in this 
area.

Mark