From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: compilation warnings
Date: Tue, 23 Sep 2003 12:19:36 -0400 [thread overview]
Message-ID: <m3wubz4gup.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87ad8wrv50.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> BTW, what version of auto* should be used to build/test CVS checkouts?
>
> The general rule of thumb is, for HEAD, the most recent stable
> versions.
That's not especially useful advice, though. After a new autoconf
release, Guile won't be updated instantly; it'll take some time.
Maybe a significant amount of time in pathological cases, but in any
case, how will we know?
Also, which tools do we need? Guile has its own libtool, right? So
just autoconf and automake?
paul
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-23 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-04 4:36 compilation warnings Paul Jarc
2003-07-27 16:56 ` Marius Vollmer
2003-07-28 22:37 ` Kevin Ryde
2003-09-22 21:58 ` Paul Jarc
2003-09-23 4:22 ` Rob Browning
2003-09-23 16:19 ` Paul Jarc [this message]
2003-09-24 6:11 ` Rob Browning
2003-10-07 16:00 ` 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=m3wubz4gup.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).