Date: Mon, 27 Jul 1998 18:36:28 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp-workers AT delorie DOT com
Subject: Re: mak3769b.zip cannot works on the makefile of Allegro.
In-Reply-To: <B0000036562@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.980727183210.1183I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 27 Jul 1998, Andris Pavenis wrote:

> The only function of these 2 scripts is to set some needed 
> environment variables (such as 'CONFIG_SHELL=bash' and some 
> others) and invoking ./configure and make when this is done.

This is not all that is needed to make configure scripts work with
DJGPP.

How do you handle the problems with "test -f gcc" etc.?
What about file names like config.h.in, po2tbl.sed.in and Makefile.in.in?
What about Makefiles which set TEXINPUTS=`pwd`:$TEXINPUTS and then run 
texi2dvi to generate printed docs?

These are just some of the problems off the top of my head.  They all 
need DJGPP-specific changes to ./configure.

> I think adding such 2 scripts is much faster as usually there is no 
> more need to edit configure script at all (maybe sometimes only to 
> rebuild it with DJGPP port of autoconf).

Using autoconf is an option, but I don't like the idea to require people 
to install it just to build a package.