From: Neil Jerram <neil@ossau.uklinux.net>
To: <guile-devel@gnu.org>
Subject: Re: [PATCH] Fix hanging of popen.test
Date: Thu, 01 Jul 2010 00:58:49 +0100 [thread overview]
Message-ID: <87bpasvzra.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87sk442l0n.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 30 Jun 2010 23:50:00 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> So my hypothesis now is:
>
> - some change in the last few months has introduced a dependency of
> Guile script startup (specifically including the case where Guile is
> run to generate guile-procedures.texi) on srfi-1.scm
>
> - this makes the build impossible!
>
> - for regular developers, this may be masked by having a libguile.so and
> libguile-srfi-srfi-13-14-v-4.so in /usr/lib or /usr/local/lib that are
> recent enough to work.
>
> Can anyone else build current git from scratch if they first hide or
> delete any guile libraries in /usr/lib and /usr/local/lib?
It occurred to me that if this is right, the Hydra build should be
failing too. And I think it is. The "gnu:guile-master:tarball" build
last succeeded on 17th June, and has been failing since then:
http://hydra.nixos.org/job/gnu/guile-master/tarball/all?page=1
next prev parent reply other threads:[~2010-06-30 23:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 22:54 [PATCH] Fix hanging of popen.test Neil Jerram
2010-06-11 19:48 ` Neil Jerram
2010-06-14 21:27 ` Andy Wingo
2010-06-28 21:48 ` Neil Jerram
2010-06-29 9:31 ` Andy Wingo
2010-06-29 19:11 ` Neil Jerram
2010-06-30 22:50 ` Neil Jerram
2010-06-30 23:58 ` Neil Jerram [this message]
2010-07-01 10:48 ` Andy Wingo
2010-07-01 20:29 ` Patrick McCarty
2010-07-03 22:17 ` Ludovic Courtès
2010-07-04 9:07 ` Andy Wingo
2010-07-04 20:33 ` Neil Jerram
2010-07-06 21:35 ` Ludovic Courtès
2010-07-17 11:57 ` Andy Wingo
2010-07-17 18:08 ` Patrick McCarty
2010-07-01 16:22 ` dsmich
2010-07-01 21:22 ` 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=87bpasvzra.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).