From: Heikki Lindholm <holindho@cs.helsinki.fi>
Cc: Guile Development <guile-devel@gnu.org>,
Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Trouble building 1.8.x
Date: Tue, 02 Jan 2007 08:58:54 +0200 [thread overview]
Message-ID: <459A02AE.9060703@cs.helsinki.fi> (raw)
In-Reply-To: <87wt46nzg3.fsf@zip.com.au>
Kevin Ryde kirjoitti:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>>+ ./autogen.sh ../workbook
>
>
> I've never used that. :)
>
>
>>autoreconf
>
>
> Nor that.
>
>
>>configure:35800: error: possibly undefined macro: AM_INTL_SUBDIR
>> If this token and others are legitimate, please use m4_pattern_allow.
>> See the Autoconf documentation.
>
>
> Sounds strange. As a wild guess though, check you haven't got any
> symlinked .m4 files in the guile-config dir (or wherever) which have
> become broken by upgrading automake and/or gettext. That bit me on my
> last update, I fixed it by deleting them.
>
> (I think it was gettextize that made those links for me. I suspect
> that's a throwback to a time when all .m4 files were supposed to be
> both in the dist as well as in aclocal.m4. I'd be surprised if anyone
> has ever used either mechanism for a reconf though.)
I also failed miserably at generating the configure scripts. So, how
about telling THE mechanism that people are using to do a reconf?
-- Heikki Lindholm
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-02 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 1:06 Trouble building 1.8.x Neil Jerram
2007-01-01 18:11 ` Neil Jerram
2007-01-01 22:40 ` Kevin Ryde
2007-01-02 6:58 ` Heikki Lindholm [this message]
2007-01-03 22:46 ` 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=459A02AE.9060703@cs.helsinki.fi \
--to=holindho@cs.helsinki.fi \
--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).