unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Greg Troxel" <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org
Subject: Re: git head fails to build
Date: Wed, 14 Jan 2009 21:07:16 +0000	[thread overview]
Message-ID: <49dd78620901141307j1facd263kc9a59a58c2426e83@mail.gmail.com> (raw)
In-Reply-To: <rmipripwqiw.fsf@fnord.ir.bbn.com>

2009/1/14 Greg Troxel <gdt@ir.bbn.com>:
>
> (has anyone else built head of git?)
>
> Now I get:
>
> list gdt 3 ~/BUILD-GUILE-1.9.0 > ./build-guile.sh
> remote: Counting objects: 8, done.
> remote: Compressing objects: 100% (5/5), done.
> remote: Total 5 (delta 3), reused 0 (delta 0)
> Unpacking objects: 100% (5/5), done.
> From git://git.sv.gnu.org/guile
>   bf4200c..0a34f39  master     -> origin/master
> Updating bf4200c..0a34f39
> Fast forward
>  m4/.gitignore      |    1 -
>  m4/localcharset.m4 |   16 ++++++++++++++++
>  2 files changed, 16 insertions(+), 1 deletions(-)
>  create mode 100644 m4/localcharset.m4
> KEEPING LOCAL CHANGES
> cd . && /bin/ksh /home/gdt/BUILD-GUILE-1.9.0/guile/build-aux/missing --run aclocal-1.10 -I m4
>  cd . && /bin/ksh /home/gdt/BUILD-GUILE-1.9.0/guile/build-aux/missing --run automake-1.10 --gnu
> cd . && /bin/ksh /home/gdt/BUILD-GUILE-1.9.0/guile/build-aux/missing --run autoconf
> configure:7956: error: possibly undefined macro: gl_FUNC_MBRLEN
>      If this token and others are legitimate, please use m4_pattern_allow.
>      See the Autoconf documentation.
> configure:7961: error: possibly undefined macro: gl_FUNC_MBRTOWC
> configure:7966: error: possibly undefined macro: gl_FUNC_MBSINIT
> gmake: *** [configure] Error 1
> Adding AB_INIT to configure.in
> 50957
> AH_TOP(/*GUILE_CONFIGURE_COPYRIGHT*/)
> 50967
> autoreconf: Entering directory `.'
> autoreconf: configure.in: not using Gettext
> autoreconf: running: aclocal --force -I m4
> autoreconf: configure.in: tracing

OK, more files added, please try once more.  I wonder why Gnulib
incorrectly adds these to m4/.gitignore?

Regards,
      Neil




  reply	other threads:[~2009-01-14 21:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 19:20 git head fails to build Greg Troxel
2009-01-14 20:05 ` Neil Jerram
2009-01-14 20:12   ` Greg Troxel
2009-01-14 20:24     ` Greg Troxel
2009-01-14 20:47       ` Ludovic Courtès
2009-01-14 20:54     ` Neil Jerram
2009-01-14 21:01       ` Greg Troxel
2009-01-14 21:07         ` Neil Jerram [this message]
2009-01-14 21:31         ` Ludovic Courtès
2009-01-14 21:30       ` Ludovic Courtès
2009-01-14 21:45         ` Neil Jerram
2009-01-15  0:20           ` Neil Jerram
2009-01-15  0:21           ` Ludovic Courtès
2009-01-15  1:25             ` Neil Jerram
2009-01-15 22:15               ` Ludovic Courtès
2009-01-15 17:22 ` Greg Troxel
2009-01-15 17:35   ` Neil Jerram
2009-01-15 17:45     ` Greg Troxel
2009-01-15 17:46       ` Neil Jerram
2009-01-15 17:48         ` Greg Troxel
2009-01-15 17:51           ` Neil Jerram
2009-01-15 23:04           ` Ludovic Courtès
2009-01-15 23:03     ` Ludovic Courtès
2009-01-17 22:40       ` Neil Jerram

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=49dd78620901141307j1facd263kc9a59a58c2426e83@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=gdt@ir.bbn.com \
    --cc=guile-devel@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).