Date:	Mon, 1 May 2000 12:00:07 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Peter J. Farley III" <pjfarley AT dellnet DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Question about running configure script
In-Reply-To:	<390cfc8d.16509140@nntp276471.nntp.dellnet.com>
Message-ID:	<Pine.SUN.3.91.1000501115937.9191J-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 1 May 2000, Peter J. Farley III wrote:

> C:\>djtar -x -v -!. co991215.tgz

The -!. part is IMHO not a good idea.  It disables the automatic
conversion of some invalid file names that are frequently met in
.tar.gz archives of the Unix origin.  djtar then prompts you for a
valid name for each of these files, which can be quite a pest if the
number of such files is large.

Why did you suggest to use that option?

> Although, as Eli Zaretskii will probably tell you, *almost* any
> GNU-style package *can* be built under DJGPP in plain DOS, there are
> sometimes cases where Win9x LFN (long-file-name) support is truly
> necessary.

I have yet to see a package that really requires LFN to be built.  A
few simple (and fairly standard) tweaks of the configuration scripts,
that's all that's needed to overcome the file-name problems.

> One addition I would make to the things
> that others have already said:  Before running the configure script,
> run the DJGPP version of "autoconf" to modify most of the
> "non-DJGPP-friendly" parts of configure.  To do this, change to the
> directory where the configure script is stored, and just say:
> 
> C:>\place\where\configure\lives>bash autoconf

This should not be necessary with the current version of ported Bash
2.03.  It supports features that make this step redundant.

- Raw text -