From: Andy Wingo <wingo@pobox.com>
To: Jeff Sparkes <jsparkes@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: make documentation fails on Cygwin 1.7.
Date: Mon, 28 Jun 2010 14:43:47 +0200 [thread overview]
Message-ID: <m3fx07z5rw.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTikNYx7Fi4cQuh0vUABxVQFQy-3UsVCJUjAK9Aqs@mail.gmail.com> (Jeff Sparkes's message of "Thu, 24 Jun 2010 11:57:57 -0400")
Hi Jeff,
On Thu 24 Jun 2010 17:57, Jeff Sparkes <jsparkes@gmail.com> writes:
> /cygdrive/c/Users/jsparkes/src/scheme/guile/guile/doc/ref//sxml-match.texi:22: Cross reference to nonexistent node `sxml simple' (perhaps incorrect sectioning?).
Odd, this. Can you grep standard-library.texi for "@node sxml simple" ?
That is a generated file, but I don't know of a problem with the
generation rules... Perhaps it is a cygwin-specific issue generating
that file.
Thanks,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-06-28 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 15:57 make documentation fails on Cygwin 1.7 Jeff Sparkes
2010-06-28 12:43 ` Andy Wingo [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=m3fx07z5rw.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jsparkes@gmail.com \
/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).