[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can no longer build.
From: |
David Kastrup |
Subject: |
Re: Can no longer build. |
Date: |
Fri, 08 Nov 2019 22:21:21 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Thomas Morley <address@hidden> writes:
> Am Fr., 8. Nov. 2019 um 16:34 Uhr schrieb David Kastrup <address@hidden>:
>>
>> 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
>>
>> ./configure --enable-checking
>> GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config
>> GUILE=/usr/bin/guile
>>
>> Apparently using GUILE_CONFIG precludes or sabotages the checks for GUILE ?
>
>
> I made the experience that I need to set GUILE_CONFIG=... *and*
> GUILE=... if I want a build which uses a not system-wide installed
> guile-version.
But I have a system-wide installed guile version at /usr/bin/guile .
It's a Guile-2.0 but that's fine for scripts. So there really is no
good reason that it isn't found.
For the Guile compiled into LilyPond, of course setting GUILE_CONFIG is
wanted (if the correct guile-config is not in the PATH).
--
David Kastrup
- Can no longer build., David Kastrup, 2019/11/08
- Re: Can no longer build., Dan Eble, 2019/11/08
- Re: Can no longer build., David Kastrup, 2019/11/08
- Re: Can no longer build., Thomas Morley, 2019/11/08
- Re: Can no longer build.,
David Kastrup <=
- Re: Can no longer build., Jonas Hahnfeld, 2019/11/09
- Re: Can no longer build., David Kastrup, 2019/11/09
- Re: Can no longer build., Jonas Hahnfeld, 2019/11/09
- Re: Can no longer build., David Kastrup, 2019/11/09
- Re: Can no longer build., Jonas Hahnfeld, 2019/11/09
- Re: Can no longer build., David Kastrup, 2019/11/09