Re: automake configure script hangs on OSF1...
Hi Ed, * Ed Hartnett wrote on Fri, Oct 07, 2005 at 12:57:26AM CEST: I am trying to install automake and an OSF1 system. I just installed autoconf, but the automake configure hangs looking for it... *snip* checking whether autoconf is installed... yes checking whether autoconf works... And there it sits, until I kill it. Try to debug it: Edit `configure', search for the string whether autoconf works and add set -x before it (and maybe `set +x' some way down) to find out which command hangs. I'd suspect the eval $am_AUTOCONF -o /dev/null conftest.ac but wouldn't have any idea why it should hang. If this is correct, you could try to execute this line manually: create conftest.ac consisting of a line with `AC_INIT', execute autoconf as above with `/bin/sh -x' to see where it hangs. Post whatever you find. Maybe autom4te finds a non-GNU m4? Which autoconf version, by the way? Cheers, Ralf
Re: creating the $(SUBDIRS) at runtime?
Simon Richter wrote: Hi, Harald Dunkel wrote: I would like to create the directories for some $SUBDIRS as needed at runtime, e.g. erm, why? Unfortunately Automake complains about the missing directories in the source tree. Yes, because the structure of the source tree is supposed to be pretty much static (in fact, your package should be able to build with the source tree on read-only media), so it doesn't make sense to name directories that aren't there. Probably a misunderstanding. The actions performed in the build directory do not depend upon an empty directory in the source tree, so why do I have to create it? (Part of the problem is that CVS doesn't allow to rename files or directories, so I would like to avoid checking in empty directories.) Regards Harri
Re: automake configure script hangs on OSF1...
Ralf Wildenhues [EMAIL PROTECTED] writes: Hi Ed, * Ed Hartnett wrote on Fri, Oct 07, 2005 at 12:57:26AM CEST: I am trying to install automake and an OSF1 system. I just installed autoconf, but the automake configure hangs looking for it... *snip* checking whether autoconf is installed... yes checking whether autoconf works... And there it sits, until I kill it. Try to debug it: Edit `configure', search for the string whether autoconf works and add set -x checking whether autoconf is installed... yes + echo configure:2262: checking whether autoconf works + 1 5 + echo checking whether autoconf works... \c + 1 6 checking whether autoconf works... + test = set + mkdir conftest + echo AC_INIT + 1 conftest/conftest.ac + echo configure:2269: cd conftest eval autoconf -o /dev/null conftest.ac + 1 5 + 1 5 2 5 before it (and maybe `set +x' some way down) to find out which command hangs. I'd suspect the eval $am_AUTOCONF -o /dev/null conftest.ac Yep, that's where it hangs. but wouldn't have any idea why it should hang. If this is correct, you could try to execute this line manually: create conftest.ac consisting of a line with `AC_INIT', execute autoconf as above with `/bin/sh -x' to see where it hangs. Post whatever you find. Sorry, not quite following you here... Maybe autom4te finds a non-GNU m4? Which autoconf version, by the way? I did install a recent gnu m4, so it's not that. (Good idea though). Here's the autoconf version: % autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Thanks, Ed -- Ed Hartnett -- [EMAIL PROTECTED]
Re: automake configure script hangs on OSF1...
Hi Ed, * Ed Hartnett wrote on Fri, Oct 07, 2005 at 02:21:34PM CEST: Ralf Wildenhues [EMAIL PROTECTED] writes: * Ed Hartnett wrote on Fri, Oct 07, 2005 at 12:57:26AM CEST: I am trying to install automake and an OSF1 system. I just installed autoconf, but the automake configure hangs looking for it... checking whether autoconf is installed... yes + echo configure:2262: checking whether autoconf works + 1 5 + echo checking whether autoconf works... \c + 1 6 checking whether autoconf works... + test = set + mkdir conftest + echo AC_INIT + 1 conftest/conftest.ac + echo configure:2269: cd conftest eval autoconf -o /dev/null conftest.ac + 1 5 + 1 5 2 5 before it (and maybe `set +x' some way down) to find out which command hangs. I'd suspect the eval $am_AUTOCONF -o /dev/null conftest.ac Yep, that's where it hangs. OK. but wouldn't have any idea why it should hang. If this is correct, you could try to execute this line manually: create conftest.ac consisting of a line with `AC_INIT', execute autoconf as above with `/bin/sh -x' to see where it hangs. Post whatever you find. Sorry, not quite following you here... Do the following (in a new directory, maybe) and check for hangs: echo AC_INIT conftest.ac eval autoconf -o /dev/null conftest.ac eval sh -x autoconf -o /dev/null conftest.ac If the last one hangs: which are the last few commands executed? If non of these hang you can try this: sed '1a\ set -x' `which autoconf` autoconf.test eval ./autoconf.test -o /dev/null conftest.ac If this does not hang either, go back to Automake's `configure' script: something must be different there: environment, shell settings. Try to find out what causes the hang, for example, by adding `set' or `env' shortly before the hang, and comparing that to the settings where it works. Sorry to sound so diffuse, but I've seen the most diverse causes for hangs (NFS or other completely unrelated network issues). Maybe autom4te finds a non-GNU m4? Which autoconf version, by the way? I did install a recent gnu m4, so it's not that. (Good idea though). Is it the first m4 in the PATH? Here's the autoconf version: % autoconf --version autoconf (GNU Autoconf) 2.59 Thanks, Ralf
Re: automake configure script hangs on OSF1...
Hi Ed, Please keep the automake list copied -- thanks! * Ed Hartnett wrote on Fri, Oct 07, 2005 at 02:42:11PM CEST: Thanks Ralf! bash-2.01$ echo AC_INIT conftest.ac bash-2.01$ eval sh -x autoconf -o /dev/null conftest.ac sh: autoconf: cannot open D'oh. Me very stupid. eval sh -x `which autoconf` -o /dev/null conftest.ac would have been better. I also tried running autoconf on my own configure.ac file, and it hangs. Does the autom4te part hang? Please try to find out, as I noted in the last mail. If it hangs: autom4te is a perl script; you can try adding `--verbose' or running it in the perl debugger, if you know your ways around perl.. So apparently, something is wrong with autoconf. In fact, make check in the autoconf directory hangs too: Yep. Cheers, Ralf ## - ## ## GNU Autoconf 2.59 test suite. ## ## - ## Executables (autoheader, autoupdate...). 1: Syntax of the shell scripts skipped (tools.at:71) 2: Syntax of the Perl scripts ok 3: autom4te cache ok 4: autoconf --trace: user macros
Re: automake configure script hangs on OSF1...
* Ed Hartnett wrote on Fri, Oct 07, 2005 at 03:00:26PM CEST: Ralf Wildenhues [EMAIL PROTECTED] writes: Please keep the automake list copied -- thanks! eval sh -x `which autoconf` -o /dev/null conftest.ac would have been better. This seems to indicate that autom4te hangs. Output attached. *snip* + eval set $AUTOM4TE --language=autoconf --output=$outfile $infile + set /home/ed/local/dana/bin/autom4te --language=autoconf --output=/dev/null conftest.ac + : autoconf: running /home/ed/local/dana/bin/autom4te --language=autoconf --output=/dev/null conftest.ac + exec /home/ed/local/dana/bin/autom4te --language=autoconf --output=/dev/null conftest.ac If it hangs: autom4te is a perl script; you can try adding `--verbose' or running it in the perl debugger, if you know your ways around perl.. On this machine perl is 5.8.0, which seems reasonably recent. But some tools on this machine are very out-of-date, so that may be the ultimate source of the problem. Well, try perl -d /home/ed/local/dana/bin/autom4te --language=autoconf --output=/dev/null conftest.ac and interrupt it to see where it hangs. `man perldebug' knows how to use the debugger. Cheers, Ralf
