From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: master build issue
Date: Thu, 04 Jun 2009 21:49:43 +0100 [thread overview]
Message-ID: <87bpp34tco.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87fxef4tvj.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Thu\, 04 Jun 2009 21\:38\:24 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> I'm also wondering if libtool v1.5.26 is a factor (as against v2.2)
> - so now trying out libtool 2.2 from Debian testing.
Yes, that seems to do the trick. So we require libtool 2.2 now... I
guess that's OK, given that it's in Debian testing.
(I'll make an appropriate update to HACKING.)
Regards,
Neil
next prev parent reply other threads:[~2009-06-04 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 1:04 master build issue Neil Jerram
2009-06-04 19:31 ` Andy Wingo
2009-06-04 20:38 ` Neil Jerram
2009-06-04 20:49 ` Neil Jerram [this message]
2009-06-04 21:42 ` Neil Jerram
2009-06-05 0:17 ` Greg Troxel
2009-06-05 3:05 ` Mike Gran
2009-06-05 22:02 ` Neil Jerram
2009-06-06 13:14 ` Ludovic Courtès
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=87bpp34tco.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).