Date: Thu, 27 Jan 2000 09:12:00 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: bash203s.zip updated
In-Reply-To: <200001262042.PAA12634@delorie.com>
Message-ID: <Pine.SUN.3.91.1000127091132.15566A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


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?

> The only way I see to make things work right is by deleting the files 
> generated by the configure script and tell folks they will have to run 
> configure themselves so the right directories are set. Any 
> suggestions or alternatives?

Running the configure script usually requires much more carefully
set-up installation than just building, even though in this case Bash
and some auxiliary tools are required by the Makefile's.  So I'd
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.  I would even consider editing Makefile's to change the value
of BUILD_DIR before packaging, if no other trick solves this.

Of course, everybody knows that I'm crazy in these matters ;-).