Re: Can no longer build.

2019-11-09 Thread David Kastrup
Jonas Hahnfeld writes: > Am Samstag, den 09.11.2019, 13:23 +0100 schrieb David Kastrup: >> Jonas Hahnfeld via Discussions on LilyPond >> development writes: >> > Am Samstag, den 09.11.2019, 12:55 +0100 schrieb David Kastrup: >> > > Jonas Hahnfeld writes: >> > > > AFAICS configure requires a

Re: Can no longer build.

2019-11-09 Thread Jonas Hahnfeld via Discussions on LilyPond development
Am Samstag, den 09.11.2019, 13:23 +0100 schrieb David Kastrup: > Jonas Hahnfeld via Discussions on LilyPond > development writes: > > Am Samstag, den 09.11.2019, 12:55 +0100 schrieb David Kastrup: > > > Jonas Hahnfeld writes: > > > > AFAICS configure requires a guile executable between

Re: Can no longer build.

2019-11-09 Thread David Kastrup
Jonas Hahnfeld via Discussions on LilyPond development writes: > Am Samstag, den 09.11.2019, 12:55 +0100 schrieb David Kastrup: >> Jonas Hahnfeld writes: >> > >> > AFAICS configure requires a guile executable between versions >> > 1.8.2 to1.9.0 (see configure.ac, line 309), unless you pass >>

Re: Can no longer build.

2019-11-09 Thread Jonas Hahnfeld via Discussions on LilyPond development
Am Samstag, den 09.11.2019, 12:55 +0100 schrieb David Kastrup: > Jonas Hahnfeld writes: > > Am Freitag, den 08.11.2019, 22:21 +0100 schrieb David Kastrup: > > > Thomas Morley writes: > > > > Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup : > > > > > I got it now. I used to

Re: Can no longer build.

2019-11-09 Thread David Kastrup
Jonas Hahnfeld writes: > Am Freitag, den 08.11.2019, 22:21 +0100 schrieb David Kastrup: >> Thomas Morley writes: >> > Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup : >> > > I got it now. I used to do >> > > ./configure --enable-checking >> > >

Re: Can no longer build.

2019-11-09 Thread Jonas Hahnfeld via Discussions on LilyPond development
Am Freitag, den 08.11.2019, 22:21 +0100 schrieb David Kastrup: > Thomas Morley writes: > > Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup : > > > I got it now. I used to do > > > ./configure --enable-checking > > > GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config > > > but that

Re: Can no longer build.

2019-11-08 Thread David Kastrup
Thomas Morley writes: > Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup : >> >> I got it now. I used to do >> >> ./configure --enable-checking >> GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config >> >> but that appears to mess up the setting of GUILE, so I need to do >> >>

Re: Can no longer build.

2019-11-08 Thread Thomas Morley
Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup : > > Dan Eble writes: > > > On Nov 8, 2019, at 09:11, David Kastrup wrote: > >> > >> So how come my lilypond-invoke-editor script starts with > >> > >> "echo no not found -s" > >> > >> as its interpreter? Note that some underlying problem

Re: Can no longer build.

2019-11-08 Thread David Kastrup
Dan Eble writes: > On Nov 8, 2019, at 09:11, David Kastrup wrote: >> >> So how come my lilypond-invoke-editor script starts with >> >> "echo no not found -s" >> >> as its interpreter? Note that some underlying problem might not be new: > > 1. What does "grep -w GUILE config.make" tell you?

Re: Can no longer build.

2019-11-08 Thread Dan Eble
On Nov 8, 2019, at 09:11, David Kastrup wrote: > > So how come my lilypond-invoke-editor script starts with > > "echo no not found -s" > > as its interpreter? Note that some underlying problem might not be new: 1. What does "grep -w GUILE config.make" tell you? (Will be the same, I guess.)

Can no longer build.

2019-11-08 Thread David Kastrup
I have the following problem: dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9 Making scripts/out/lilypond-invoke-editor.1 help2man: can't get `--help' info from out/lilypond-invoke-editor Try `--no-discard-stderr' if option outputs to stderr make[1]: ***