On Thu 01 Jul 2010 00:58, Neil Jerram <n...@ossau.uklinux.net> writes:
> Neil Jerram <n...@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 This has been an on-and-off issue: 02fcbf78b27788c03563e5c3d297a4cd469ce562, and 04af4c4c5221c082905d52eb5ad3829ed681d097. Indeed running the repl before srfi-1 is built should not work. As a corollary, the docstring texi thing should not require srfi-1 to work, which obviously is failing for you and hydra, though not for me and a number of other people. I don't really get it. I thought this was fixed. There have been a couple threads about this, even, if you search the archives in recent months. Can you look in the output of `meta/uninstalled-env env' for any off paths? What about in %load-path / %load-compiled-path ? At the same time there must be an issue there somehow, or the tarball buildbot would not be failing (surely?). Andy -- http://wingolog.org/
