From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: autoconf and makeinfo issues (doc/ref has problems) (RC?).
Date: 03 Apr 2002 22:40:55 +0100 [thread overview]
Message-ID: <m3sn6cv4t4.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <87sn6c23o0.fsf@raven.i.defaultvalue.org>
>>>>> "Rob" == Rob Browning <rlb@defaultvalue.org> writes:
Rob> Rob Browning <rlb@defaultvalue.org> writes:
>> I've nearly finished fixing the autoconf 2.53 issues in 1.6, but now
>> I've run in to a show-stopping makeinfo problem (is this a makeinfo
>> version issue?)
Rob> OK, fixed it for now by just commenting out the program.texi include
Rob> and deleting the "Programming Overview" node from guile.texi.
Sorry, my fault, I forgot to commit program.texi.
It's there now, so you should be able to reinstate the include and
menu item for it.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-04-03 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 6:43 autoconf and makeinfo issues (doc/ref has problems) (RC?) Rob Browning
2002-04-03 15:38 ` Rob Browning
2002-04-03 21:40 ` Neil Jerram [this message]
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=m3sn6cv4t4.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).