[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Non-portable m4 check in autoconf 2.64, 2.65, HEAD
From: |
Harald van Dijk |
Subject: |
Non-portable m4 check in autoconf 2.64, 2.65, HEAD |
Date: |
Wed, 25 Nov 2009 19:53:47 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
Hi,
The configure script of autoconf 2.64/2.65/HEAD fails to detect a
suitable m4 on my system. It aborts with
autoconf-2.65 0 $ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether /bin/sh -n is known to work... no
checking for characters that cannot appear in file names... none
checking whether directories can have trailing spaces... yes
checking for expr... /usr/bin/expr
checking for GNU M4 that supports accurate traces... configure: error:
no acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.13 is recommended
I have GNU M4 1.4.13. The problem is that I'm using dash for /bin/sh
(and my dash supports LINENO so configure doesn't silently use bash
instead), and the m4 detection doesn't work when echo \1 prints ^A.
With the attached obvious patch, configure passes, and there's no
problem further on.
autoconf-m4.patch
Description: Text document
- Non-portable m4 check in autoconf 2.64, 2.65, HEAD,
Harald van Dijk <=