From: Bruno Haible <bruno@clisp.org>
Cc: guile-devel@gnu.org, Marius Vollmer <marius.vollmer@uni-dortmund.de>
Subject: Re: building guile from CVS
Date: Mon, 24 Jan 2005 16:25:25 +0100 [thread overview]
Message-ID: <200501241625.25636.bruno@clisp.org> (raw)
In-Reply-To: <87r7kee9rh.fsf@zip.com.au>
Kevin Ryde wrote:
> > 5) Since AM_GNU_GETTEXT is used in configure.in, a config.rpath is
> > needed. autoreconf does not add it. 'autopoint' would add it, but is not
> > invoked from autoreconf.
>
> Ah, yep. A gettextize is definitely now needed in autogen.sh.
No no no. gettextize is not suitable for running from within autogen.sh;
this is explained in the GNU gettext manual. You need autopoint instead.
> autoreconf won't run that.
Actually, autoreconf will do this if you add a AM_GNU_GETTEXT_VERSION
declaration in configure.in. But before doing that, run gettextize
once and _just_once_; then you put the AM_GNU_GETTEXT_VERSION line into
configure.in, with a version number that matches the one of gettextize
that you ran.
> > 6) "make" fails in the doc directory because version.texi doesn't exist.
> > Kevin Rude says that it should be fixed by
> > "configure --enable-maintainer-mode". But it would be better if
> > autogen.sh would solve this.
>
> I'm not sure autogen.sh should get involved in that.
autogen.sh is preferrable here because the creation of a version.texi is a
once-only thing. It's not needed in further runs. And not everyone using
a CVS snapshot is a maintainer.
Bruno
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-01-24 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 22:48 doc gettext Kevin Ryde
2005-01-10 21:11 ` Bruno Haible
2005-01-23 23:20 ` Kevin Ryde
[not found] ` <200501202239.07346.bruno@clisp.org>
[not found] ` <87d5vzd6bb.fsf@zip.com.au>
2005-01-21 12:09 ` building guile from CVS Bruno Haible
2005-01-21 14:06 ` Marius Vollmer
2005-01-21 15:41 ` Bruno Haible
2005-01-21 21:45 ` Kevin Ryde
2005-01-22 14:03 ` Marius Vollmer
2005-01-24 15:25 ` Bruno Haible [this message]
2005-02-28 1:17 ` Marius Vollmer
2005-02-28 1:31 ` 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=200501241625.25636.bruno@clisp.org \
--to=bruno@clisp.org \
--cc=guile-devel@gnu.org \
--cc=marius.vollmer@uni-dortmund.de \
/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).