[Top][All Lists]

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

AC_OUTPUT to parent dir and install-sh

From: Willem Jan Palenstijn
Subject: AC_OUTPUT to parent dir and install-sh
Date: Sun, 19 Jul 2009 22:52:57 +0000
User-agent: Mutt/1.5.13 (2006-08-11)


Is it allowed to list files in the parent directory of the
main source directory in AC_CONFIG_FILES? I'm trying the following small

AC_INIT(testcase, 0.0.1, address@hidden)
AC_CONFIG_FILES([test ../test_parent])

When I use autoconf-2.63 with this, and run the resulting configure
script, and there is no 'install' program in $PATH, the script
'./install-sh' is used as $INSTALL. In the 'test' output file, @INSTALL@
is then correctly replaced by './'. However, in
'../test_parent' @INSTALL@ is replaced by '.././', which does
not exist.

At a cursory glance, it seems config.status is counting slashes in
'../test_parent' and concluding test_parent is in a subdirectory of the
source directory.

Is this expected behaviour? I couldn't find any reference in the
autoconf documentation or on the mailing list to this case, but I may
have overlooked it.

Should it be useful, I prepared a small tarball with the example and the other necessary files at .

Aside: this issue popped up when building the Singular
( ) mathematics package which uses
autoconf. It uses multiple configure scripts, one of which is in one
subdirectory of the root and generates a Makefile in another
subdirectory of the root. It was encountered by a Sage ( ) developer who was building a patched Singular
as part of Sage on a Solaris machine that did not have an 'install'

With kind regards,
Willem Jan

reply via email to

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