From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Guile automated builds available
Date: Wed, 10 Sep 2008 23:18:10 +0200 [thread overview]
Message-ID: <49dd78620809101418t1f514e91w93be13e2664ee2b7@mail.gmail.com> (raw)
In-Reply-To: <87ljz2d7ec.fsf@gnu.org>
Hi Ludo, sorry that this is so late...!
2008/8/12 Ludovic Courtès <ludo@gnu.org>:
> Hello,
>
> I've installed a daily build process on some of the GCC Compile Farm
> Project's machines [0], currently covering 3 architectures (sparc64,
> alphaev56 and x86-64), all under GNU/Linux, with different versions of
> GCC. From now on, the build should run at around 3pm UTC every day.
> Build logs are sent by mail to Simon Josefsson's Autobuild service [1]
> and can be seen here:
>
> http://autobuild.josefsson.org/guile/
This looks really useful!
> I use a simple script (attached) that invokes Autobuild's m4 macro [2].
> I'm wondering whether it would be a good idea to include it in releases,
> and tell people they can run
> "./configure && make check | mail guile@autobuild.josefsson.org" so that
> we get more build results.
>
> Thoughts?
I think that's an excellent idea. Just to check that I'm
understanding correctly: I believe you mean just adding AB_INIT to
configure.in, and the source for AB_INIT to acinclude.m4; is that
right?
Regards,
Neil
next prev parent reply other threads:[~2008-09-10 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 7:22 Guile automated builds available Ludovic Courtès
2008-09-10 21:18 ` Neil Jerram [this message]
2008-09-11 10:21 ` 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=49dd78620809101418t1f514e91w93be13e2664ee2b7@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).