[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
configure quotes problem under Tru64 unix
From: |
Nicolas Joly |
Subject: |
configure quotes problem under Tru64 unix |
Date: |
Tue, 28 Aug 2001 11:18:04 +0200 |
User-agent: |
Mutt/1.2.5i |
Hi,
I just found a small problem with CVS autoconf under Tru64 unix.
address@hidden [temp/autoconf]> ./configure
./configure: $/d confdefs.h
echo
fi
test "$ac_signal" != 0 &&
echo "$as_me: caught signal $ac_signal"
echo "$as_me: exit $exit_status"
} >&5
rm -rf conftest* confdefs* core core.* *.core conf$$* $ac_clean_files &&
exit $exit_status
: not found
checking for a BSD compatible install... config/install-sh -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
[...]
This problem is located in `lib/autoconf/general.m4' :
# When interrupted or exit'd, cleanup temporary files, and complete
# config.log. We remove comments because anyway the quotes in there
# would cause problems or look ugly.
trap 'exit_status=$?
# Save into config.log some information that might help in debugging.
{
echo
AS_BOX([Cache variables.])
echo
[...]
if test -s confdefs.h; then
AS_BOX([confdefs.h.])
echo
sed '/^$/d' confdefs.h
echo
fi
} >&AS_MESSAGE_LOG_FD
rm -rf conftest* confdefs* core core.* *.core conf$[$]* $ac_clean_files &&
exit $exit_status
' 0
The `trap' and `sed' quotes conflicts with Tru64 `/bin/sh' (but it
seems to work fine with both ksh and zsh). Using double quotes for the
`sed' call solves the problem.
Thanks in advance.
--
Nicolas Joly
Informatique Scientifique
Institut Pasteur, Paris.
- configure quotes problem under Tru64 unix,
Nicolas Joly <=