From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Guile Bugs <bug-guile@gnu.org>
Subject: Re: Building without makeinfo
Date: 15 Mar 2002 00:54:55 +0100 [thread overview]
Message-ID: <87heniwvqo.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3wuwn6ja7.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> However, wouldn't a better fix be to include a prebuilt
> guile-procedures.txt in the distribution? If I understand correctly,
> all we would need to do is
>
> - add guile-procedures.txt to EXTRA_DIST
>
> - remove the `else' branch of the `if HAVE_MAKEINFO' block.
>
> What do you think?
Conceptually, guile-procedures.txt is dependent on the configuration
of Guile. So, strictly speaking, we can't distribute the 'right'
guile-procedures.txt file.
But, we can probably distribute one that is almost always right, but
we have to be careful when generating it.
I.e. when Guile has been configured --without-threads,
guile-procedures.txt wont contain the docs for the threading
functions.
So, when we have a good way to create a default guile-procedures.txt,
then I'd say we should distribute it.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next parent reply other threads:[~2002-03-14 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3wuwn6ja7.fsf@laruns.ossau.uklinux.net>
2002-03-14 23:54 ` Marius Vollmer [this message]
2002-03-15 9:03 ` Building without makeinfo Neil Jerram
2002-03-15 21:20 ` Marius Vollmer
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=87heniwvqo.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@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).