Jan Nieuwenhuizen writes:
> David Kastrup writes:
>
>> Actually not even
>>
>> rm -rf scripts/out
>>
>> did the trick
>
> What about
>
>rm -rf python/out
Well, it is likely python/out/relocate_preample.py that is responsible
here, possibly through python/out/lilylib.py.
> If that does n
David Kastrup writes:
> Actually not even
>
> rm -rf scripts/out
>
> did the trick
What about
rm -rf python/out
If that does not work, can we please have a nice bug report
with a minimal recipe that exhibits this problem?
Jan
--
Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
Fr
On Tue, May 10, 2011 at 12:28:54PM +0200, David Kastrup wrote:
>
> Any possibility of fixing the dependencies in a manner that a changed
> version will lead to appropriately changed python scripts?
No, I do not envision any realistic possibility.
To cut through to the heart of the matter: buildi
When installing the Python scripts, those contain references to
directories /usr/local/lib/lilypond/2.13.58 and
/usr/local/share/lilypond/2.13.58 which are outdated.
What's up with that?
./autogen.sh
does not help.
I am now doing "make clean all info" which would appear to put sensible
directo
