From: "Tim Van Holder" To: Subject: RE: Two glitches for autoconf 2.49b Date: Mon, 1 Jan 2001 12:54:42 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id GAA29289 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > How are these files called originally? Is it config.guess.1 and > config.sub.1? Yes. > If you call the files under man/cat1/ config.guess and config.sub, does > "man config.guess" and "man config.sub" work with the DJGPP clone of > `man' (v2apps/man13b.zip)? If so, you don't need to rename. It doesn't. IIRC, man checks an extension for certain characters (which, annoyingly, causes it to think autoconf.bz2 is a man page, while it is actually a bzip2-compressed info file - but it's easy enough to remove $DJDIR/info from the manpath). > If that doesn't work, I don't see anything wrong with config_*.1; I did > that in the Groff port. If you say this in the README, whoever wants the > docs will find it. I suppose it'll do. > I'd expect that setting SHELL alone will do, even without rebuilding m4. > __system_use_shell is set by default (see the beginning of system.c), and > __system_call_cmdproc is irrelevant to this case, since Bash will be > recognized by the library as a Unixy shell. Here's the relevant fragment > from system.c: > > call_shell = > (sys_flags & __system_call_cmdproc) > || (!(sys_flags & __system_emulate_command) && _is_unixy_shell (shell)); > > Your case is the second part of the condition: __system_emulate_command > is _not_ set in sys_flags, and the shell is a Unixy one. Aha - tried and you are indeed correct. Well then, thanks for the info. The annoying thing is that I don't remember why I originally stripped the extension of $SHELL. > the script. Another way is to have a private config.site file, or some > other file which Bash source's when it runs ./configure. > If setting $SHELL alone somehow doesn't work, please tell the details. It works fine. Thanks.