Re: Trouble building 1.8.x

2007-01-01 Thread Neil Jerram
Neil Jerram <[EMAIL PROTECTED]> writes: > I'm struggling to rebuild 1.8.x after a cvs update. > > I installed the latest automake (1.10), autoconf (2.61), libtool > (1.5.22) and gettext (0.16) into /usr/local, but I still find that > ./autogen.sh fails: [...] > configure:35800: error: possibly

Re: More i18n

2007-01-01 Thread Kevin Ryde
Neil Jerram <[EMAIL PROTECTED]> writes: > > Not sure about 1..12 though; 0-based indices are a pretty well > established convention in Scheme, aren't they? 0 to 6 on weekday names would be ok. But on the months I think 1 to 12 would be more helpful, and probably less error-prone if you're mostly

Re: Trouble building 1.8.x

2007-01-01 Thread Kevin Ryde
Neil Jerram <[EMAIL PROTECTED]> writes: > > + ./autogen.sh ../workbook I've never used that. :) > autoreconf Nor that. > configure:35800: error: possibly undefined macro: AM_INTL_SUBDIR > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf docume

Re: top-repl priority of guile module

2007-01-01 Thread Kevin Ryde
Neil Jerram <[EMAIL PROTECTED]> writes: > > Absolutely, yes. One day we should get to de-polluting the guile-user > namespace ... Document or hide. > Yes, except that I think Kevin's patch using process-use-modules is > even better, because it avoids needing the resolve-interface calls, > and al

gc-stats: adding scm_total_cells_allocated ?

2007-01-01 Thread Han-Wen Nienhuys
Hello, would people mind if I added a total-cells-allocated field to the (gc-stats) output? I'm trying to do memory profiling on runs of lilypond, but there is no way to determine how much memory a function call uses, since memory usage according to gc-stats depends on whether GC occurs durin

Re: Trouble building 1.8.x

2007-01-01 Thread Heikki Lindholm
Kevin Ryde kirjoitti: Neil Jerram <[EMAIL PROTECTED]> writes: + ./autogen.sh ../workbook I've never used that. :) autoreconf Nor that. configure:35800: error: possibly undefined macro: AM_INTL_SUBDIR If this token and others are legitimate, please use m4_pattern_allow. See