From: "Ed Manlove" Newsgroups: comp.os.msdos.djgpp References: Subject: Re: Autoconf can't find m4 Lines: 45 X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: Date: Tue, 26 Nov 2002 08:33:34 -0500 NNTP-Posting-Host: 207.207.244.13 X-Complaints-To: news AT netcarrier DOT com X-Trace: news.netcarrier.net 1038315693 207.207.244.13 (Tue, 26 Nov 2002 08:01:33 EST) NNTP-Posting-Date: Tue, 26 Nov 2002 08:01:33 EST Organization: NetCarrier Internet Services To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli, Thank you for your assistance. I was unaware of the need for Perl for autoconf. And although I had ActiveState Active Perl installed I download the DJGPP Perl port. I believe my cross compiler was in an "illegal" state or just a bad state. When I reinstalled everything I was unable to get it into the mode I had it in before this error arrived. Thanks again for the support. Ed Eli Zaretskii wrote in message news:Pine DOT SUN DOT 3 DOT 91 DOT 1021119074644 DOT 10110C-100000 AT is... > > On Mon, 18 Nov 2002, Ed Manlove wrote: > > > I am getting the following error in building a cross compiler. It states > > autoconf can't find m4 but it is in my bin directory and my path is there? > > Any ideas? > > [...] > > make.exe[1]: Entering directory `c:/djgpp/gnu/gcc-2.952/build.djg/gcc' > > cd ../../gcc; autoconf > > autoconf: Autoconf requires GNU m4 1.4 or later > > make.exe[1]: *** [../../gcc/configure] Error 1 > > Sorry for asking the obvious: you do have Autoconf installed, right? > > If you do, the next things I'd suggest to look into are: > > - Is m4.exe a DJGPP port? If not, perhaps Autoconf invokes it in a way > that fails due to compatibility problems (such as long command lines). > Or maybe the m4 you have is not version 1.4 or later (type > "m4 --version" and see what it says). > > - Do you have Perl and Bash installed? IIRC, Autoconf is a Perl > script, so it requires Perl and Bash. > > - Finally, find out what code fragment in Autoconf prints the above > error message and try to figure out why could it fail. If you cannot > figure that out, post the failing fragment here and someone will help > you out.