From: Neil Jerram <neil@ossau.uklinux.net>
To: Guile Development <guile-devel@gnu.org>
Subject: autohackery and nightly snapshots
Date: Wed, 21 Feb 2007 21:32:26 +0000 [thread overview]
Message-ID: <87ejoj5h91.fsf@ossau.uklinux.net> (raw)
I finally got to the bottom of all the gettext, config.rpath, m4 and
automake nonsense that's been turning my brain to mush. As a result,
I'm happy to report that the 1.8 snapshot is now building again, and
the HEAD snapshot is getting a lot further than it has for the last
few months.
For anyone interested...
- The automake/m4 tracing problem that complains incorrectly about
AM_INTL_SUBDIR being missing has in fact been fixed in m4. I had
installed a fixed m4 in /usr/local/bin, but autom4te hardcodes
/usr/bin/m4 (even when autom4te is itself in /usr/local/bin), so
wasn't getting the fix.
The solution for this is either to have a fixed m4 in /usr/bin, or
to "export M4=/usr/local/bin/m4" before running ./autogen.sh. Then
the dummy definition of AM_INTL_SUBDIR in acinclude.m4 isn't needed
(and so I've backed this out).
- config.rpath is required at autogen time, so long as the installed
gettext is recent enough. Older gettexts (such as on the nightly
snapshot machine) do not enforce this, so the build on such machines
goes past this check and appears to succeed.
So config.rpath should be in CVS, and now is in 1.8 and HEAD branches.
- config.rpath does not need to be listed in EXTRA_DIST, however.
So long as config.rpath is present, automake includes it in
DIST_COMMON, which means it gets into the distribution.
(The HEAD snapshot is now failing on i18n.test when doing a "make
distcheck", because of a (load-extension "libguile-i18n-v-0" ...) call
not being able to find the library. I suspect the solution is this:
--- pre-inst-guile.in 17 Apr 2006 00:18:11 -0000 1.8
+++ pre-inst-guile.in 21 Feb 2007 21:31:16 -0000
@@ -43,7 +43,7 @@
# Code:
# config
-subdirs_with_ltlibs="srfi guile-readline" # maintain me
+subdirs_with_ltlibs="srfi guile-readline libguile" # maintain me
# env (set by configure)
top_srcdir="@top_srcdir_absolute@"
but I'm still investigating.)
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2007-02-21 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 21:32 Neil Jerram [this message]
2007-02-21 23:03 ` autohackery and nightly snapshots Kevin Ryde
2007-02-22 9:32 ` Ludovic Courtès
2007-02-22 19:24 ` Neil Jerram
2007-02-24 22:45 ` Neil Jerram
2007-02-25 22:43 ` Kevin Ryde
2007-02-26 20:15 ` Neil Jerram
2007-02-26 22:28 ` Kevin Ryde
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=87ejoj5h91.fsf@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).