From: Kevin Ryde <user42@zip.com.au>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Patch to fix working of autogen.sh
Date: Thu, 08 Feb 2007 10:23:50 +1100 [thread overview]
Message-ID: <87bqk5eem1.fsf@zip.com.au> (raw)
In-Reply-To: <87ejp2oovb.fsf@ossau.uklinux.net> (Neil Jerram's message of "Tue, 06 Feb 2007 23:19:52 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> (1) autoreconf exits with error status, because it thinks that the
> expansion of AM_GNU_GETTEXT requires a definition of
> AM_INTL_SUBDIR, and AM_INTL_SUBDIR isn't defined.
If it thinks that then I guess it's not recognising "external" in
AM_GNU_GETTEXT.
> (2) If you get past (1), one of the subsequent build steps (forget
> which one) fails because there is no config.rpath in the top level
> directory.
I don't remember how I got that into my working dir. I expect it was
from running gettextize then reverting the excessive changes that
program makes.
> I understand that (1) is caused by an inconsistency between aclocal
> and autoconf. When aclocal decides what macros we need in aclocal.m4,
> it correctly decides that we don't need AM_INTL_SUBDIR. When autoconf
> checks that we have all the macros that we need, it incorrectly thinks
> we do need AM_INTL_SUBDIR.
Yep. Sounds very fishy. Is this the latest and greatest gettext
macros?
> - config.rpath is apparently required for linking to the gettext
> library (which Guile genuinely needs, I believe),
Yep.
> - autopoint only runs, however, if configure.in contains both
> AM_GNU_GETTEXT and AM_GNU_GETTEXT_VERSION
>
> - therefore I solved (2) by adding AM_GNU_GETTEXT_VERSION ...
Not that there's anything stopping us running it explicitly of course,
if we know it's needed ...
> We could make (1) more palatable by actually starting to
> internationalize Guile's internal strings - so then we would really
> need the po directory!
Depends I guess if anyone wants to work on that. Could do an en_AU
translation, by adding "bloody" and "strewth" at various places :-)
<unnamed port>:1:1: Wrong bloody type (expecting pair): x
> On the other hand, (2) has the benefit that it should allow the
> nightly snapshot to build. (I now know from the build machine's log
> that the snapshot is failing because autopoint is not installed on the
> build machine.)
That doesn't mean it's an old (old-ish) gettext does it?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-02-07 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 9:44 Patch to fix working of autogen.sh Neil Jerram
2007-01-28 16:00 ` Neil Jerram
2007-01-29 23:48 ` Kevin Ryde
2007-02-06 23:19 ` Neil Jerram
2007-02-07 23:23 ` Kevin Ryde [this message]
2007-02-18 23:21 ` Neil Jerram
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=87bqk5eem1.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).