bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem with autoconf 2.57?


From: corlette
Subject: Problem with autoconf 2.57?
Date: Sat, 18 Oct 2003 00:24:50 -0400

Hello,

I found the following bug (?) in a configure script reportedly 
generated with GNU autoconf 2.57.

Environment: 
QNX 4.24
ksh
Attempting to configure ntpd 4.2.0

AFAICT, there are serious problems with the "sed" command lines 
generated in the $as_tr_cpp and $as_tr_sh variables:
---------BROKEN------------
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="sed 
y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g

# Sed expression to map a string onto a valid variable name.
as_tr_sh="sed y%*+%pp%;s%[^_$as_cr_alnum]%_%g"
-----------------
In my OS, the ';' in  the middle of the sed command is interpreted as 
a end-of-line in the shell, not as a sed command separator.  The 
result is that many tests fail, in part because confdefs.h defines 
the wrong macros (#define HAVE_SYS/TYPES_H 1).

The solution is to replace the ';' with ' -e ', and insert another ' -
e ' just after 'sed':
-------FIXED--------
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="sed -e y%*$as_cr_letters%P$as_cr_LETTERS% -e 
s%[^_$as_cr_alnum]%_%g

# Sed expression to map a string onto a valid variable name.
as_tr_sh="sed -e y%*+%pp% -e s%[^_$as_cr_alnum]%_%g"
-----------------

I don't know if this is just a QNX problem, but it would seem that 
the same would be true in other environments, c.f. this selection 
from the OpenBSD manual for sed:
"A single command may be specified as the first argument to sed.  
Multiple commands may be specified by using the -e or -f options."
Note that there is no mention of using ';' as a separator for sed 
commands.

Thanks!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]