From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: what am I doing wrong building 1.8?
Date: Mon, 13 Aug 2007 23:27:42 +0200 [thread overview]
Message-ID: <874pj3w2ep.fsf@pobox.com> (raw)
In-Reply-To: <87absvw325.fsf@pobox.com> (Andy Wingo's message of "Mon\, 13 Aug 2007 23\:13\:38 +0200")
A followup problem:
[Should these go to bug-guile or something?]
make[3]: Entering directory `/home/wingo/src/guile-1.8/doc/ref'
GUILE="/home/wingo/src/guile-1.8/pre-inst-guile" ../../scripts/snarf-guile-m4-docs ../../guile-config/guile.m4 > ./autoconf-macros.texi
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /home/wingo/src/guile-1.8/build-aux/missing --run makeinfo --version) >/dev/null 2>&1; then \
for f in guile.info guile.info-[0-9] guile.info-[0-9][0-9] guile.i[0-9] guile.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /home/wingo/src/guile-1.8/build-aux/missing --run makeinfo -I . \
-o guile.info guile.texi; \
then \
rc=0; \
cd .; \
else \
rc=$?; \
cd . && \
$restore $backupdir/* `echo "./guile.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
guile.texi:9: @include `version.texi': No such file or directory.
guile.texi:27: warning: undefined flag: VERSION.
guile.texi:164: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//preface.texi:15: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//intro.texi:72: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//intro.texi:75: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//intro.texi:80: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//intro.texi:83: warning: undefined flag: VERSION.
/home/wingo/src/guile-1.8/doc/ref//intro.texi:89: warning: undefined flag: VERSION.
makeinfo: Removing output file `guile.info' due to errors; use --force to preserve.
make[3]: *** [guile.info] Error 1
make[3]: Leaving directory `/home/wingo/src/guile-1.8/doc/ref'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/wingo/src/guile-1.8/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/wingo/src/guile-1.8'
make: *** [all] Error 2
If I pass --enable-maintainer-mode to configure this problem goes away,
and the build completes. Is this expected?
Regards,
Andy.
--
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-13 21:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 21:13 what am I doing wrong building 1.8? Andy Wingo
2007-08-13 21:27 ` Andy Wingo [this message]
2007-08-14 8:59 ` Ludovic Courtès
2007-08-14 19:27 ` Andy Wingo
2007-08-14 9:18 ` Ludovic Courtès
2007-08-14 15:05 ` Ludovic Courtès
2007-08-14 22:47 ` Neil Jerram
2007-08-16 10:28 ` Ludovic Courtès
2007-08-19 13:17 ` Marijn Schouten (hkBst)
2007-08-20 8:02 ` Ludovic Courtès
2007-08-20 12:06 ` Marijn Schouten (hkBst)
2007-08-20 14:48 ` Ludovic Courtès
2007-08-20 15:16 ` Marijn Schouten (hkBst)
2007-08-21 7:41 ` Ludovic Courtès
2007-08-21 14:12 ` Marijn Schouten (hkBst)
2007-08-22 8:01 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874pj3w2ep.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).