From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Bugs <bug-guile@gnu.org>, Rob Browning <rlb@defaultvalue.org>
Subject: Re: Trouble building stable branch right now
Date: 15 Apr 2002 00:12:00 +0100 [thread overview]
Message-ID: <m31ydhswn3.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <87pu12nirr.fsf@zagadka.ping.de>
>>>>> "Marius" == Marius Vollmer <mvo@zagadka.ping.de> writes:
Marius> I don't know where your specific errors come from, but we now seem to
Marius> require at least autoconf 2.53, automake 1.5, and a matching libtool
Marius> (not sure about the exact version yet).
Marius> I have changed configure.in to require autoconf 2.53, and the top
Marius> Makefile.am to require automake 1.5.
OK, build is fine now. Sorry for missing the new requirement.
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-04-14 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 12:53 Trouble building stable branch right now Neil Jerram
2002-04-14 20:10 ` Marius Vollmer
2002-04-14 23:12 ` Neil Jerram [this message]
2002-04-15 12:16 ` 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=m31ydhswn3.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=rlb@defaultvalue.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).