unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: branch_release-1-8 not building
Date: Sun, 14 Dec 2008 14:53:59 +0000	[thread overview]
Message-ID: <49dd78620812140653s497db9c9na8bad29b334e44b9@mail.gmail.com> (raw)
In-Reply-To: <87k5a69ydg.fsf@gnu.org>

2008/12/11 Ludovic Courtès <ludo@gnu.org>:
>
> Yes, `autoreconf' recurses.  I'd happily live without `autogen.sh', but
> feel free to update it to fit your needs.

Thanks, I've done that now.

Personally I do think it's useful to have a top level autogen.sh; it's
almost standard to have one, so I think it's a nice cue for new
developers.  (If we didn't have it, I guess we should instead document
our canonical build process in HACKING; that would be OK too IMO.)

    Neil




      reply	other threads:[~2008-12-14 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 22:10 branch_release-1-8 not building Neil Jerram
2008-12-10 23:38 ` Ludovic Courtès
2008-12-11  0:08   ` Neil Jerram
2008-12-11 21:48     ` Ludovic Courtès
2008-12-14 14:53       ` Neil Jerram [this message]

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=49dd78620812140653s497db9c9na8bad29b334e44b9@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).