This is the mail archive of the
guile@sources.redhat.com
mailing list for the Guile project.
Problems running guile-doc-snarf
- To: "Greg J. Badros" <gjb at cs dot washington dot edu>
- Subject: Problems running guile-doc-snarf
- From: Shawn <sabetts at tiny>
- Date: Thu, 13 Jul 2000 23:23:09 -0700
- CC: guile at sourceware dot cygnus dot com
After installing guile-1.4, I tried running guile-doc-snarf on some
code and it gave me this message:
mawk: cannot open guile-func-name-check (No such file or directory)
I noticed guile-func-name-check was in my path, but the
guile-doc-snarf script assumes its in the current directory as seen by
this line in guile-doc-snarf:
${AWK} -f guile-func-name-check "$fullfilename"
So I made a quick patch...Thinking about it now, I don't see why the line:
guile-func-name-check "$fullfilename"
wouldn't work just as well.
--- ./contrib/guile-1.4/libguile/guile-doc-snarf Thu Jun 29 21:09:33 2000
+++ /usr/local/bin/guile-doc-snarf Wed Jul 12 22:55:59 2000
@@ -23,7 +23,7 @@
test -n "${AWK+set}" || AWK="mawk"
## Must run guile-func-name-check on the unpreprocessed source
-${AWK} -f guile-func-name-check "$fullfilename"
+${AWK} -f `which guile-func-name-check` "$fullfilename"
## We must use a temporary file here, instead of a pipe, because we
## need to know if CPP exits with a non-zero status.