From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: indent upgrade Date: 3 Jun 2003 10:39:09 GMT Organization: Aachen University of Technology (RWTH) Lines: 28 Message-ID: References: <3EDB22ED DOT 188CC8A3 AT yahoo DOT com> <4098-Tue03Jun2003072457+0300-eliz AT elta DOT co DOT il> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1054636749 24212 137.226.32.75 (3 Jun 2003 10:39:09 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 3 Jun 2003 10:39:09 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: >> From: CBFalconer [...] >> I haven't the vaguest idea what that configure script is doing, >> except it appears to run sh and sed incessantly, with an >> occasional call to chmod. > The configure script probes the target system for the exdistence of > header files and library functions that might or might not exist, [...] I don't think that's what Chuck was asking. In the case at hand, the configure script he ran never got to that phase of its activities. It obviously was a new-style one (made by autoconf-2.57 or so). Those first copy themselves to a new file 'configure.lineno' with line numbers subsituted in for error messaging, and that process appears to be rather sensitive to minor flaws in the shell. E.g. if you try that with the Digital Unix default /bin/sh, it'll run into an endless loop --- you need their special POSIX version of Bourne shell to do it. It might already make a difference whether you run configure as "./configure" from inside an interactive bash or "bash configure" from command.com, in this case. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.