X-Authentication-Warning: new-smtp2.ihug.com.au: Host p58-max49.syd.ihug.com.au [203.173.144.122] claimed to be acceleron
Message-ID: <00da01c11d65$77f853b0$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp-workers AT delorie DOT com>
Subject: DJGPP Grep config query
Date: Sun, 5 Aug 2001 14:16:57 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Reply-To: djgpp-workers AT delorie DOT com

Eli,

I can now build grep on Win2K if I use the makefile or modify the config.bat
file. If I run the djgpp\config.bat file without modifications that the
following error occurs:

DJGPP_204 D:\dj204\gnu\grep-2.4>djgpp\config
Configuring GNU Grep for DJGPP v2.x...
Updating configuration scripts...
Running the ./configure script...
loading site script ./djgpp/config.site
loading cache ./config.cache
checking for a BSD compatible install... /dev/env/DJDIR/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... found
checking for working makeinfo... missing
checking host system type... configure: error: can not guess host type; you
must
 specify one
./configure script exited abnormally!

I get the same error on my Win98 box, but aclocal, autoconf, automake,
makeinfo are found as I have perl installed. This is not stopping my testing
on Win2K.

If i add "--target=i586-pc-msdosdjgpp --host=i586-pc-msdosdjgpp" to the
configure line in the config.bat file I can then re-configure grep & build
it. The updated config line is
sh
./configure --src=%XSRC% --disable-nls --target=i586-pc-msdosdjgpp --host=i5
86-pc-msdosdjgpp

The origianl config.bat line was
sh ./configure --src=%XSRC% --disable-nls

Does this mean that I will find other packages with a similar problem?  Is
the real problem that when the packages were first built there was no
support for the configure scripts and now there is?

Regards.
Andrew