Re: compilation error

[John Mandereau]

On 2008/11/11 15:49 +0100, Werner LEMBERG wrote:
> Another potential problem comes to my mind: Where exactly are
> lilypond's python modules installed after `make install'?  Is it
> possible that python uses lilypond PYC files which have been installed
> already, instead of using python files of the current build?

It seems to happen on your system, the log you sent says:
# /usr/local/share/lilypond/2.11.64/python/musicexp.pyc matches 
/usr/local/share/lilypond/2.11.64/python/musicexp.py
import musicexp # precompiled from 
/usr/local/share/lilypond/2.11.64/python/musicexp.pyc


> I haven't done a `make uninstall' of the previous lilypond version
> before doing a `make all' with the new version -- and, to be honest,
> this must never, ever be a prerequisite.

I agree, but I can't reproduce this issue.  What's the value of
PYTHONPATH on your system?  Even if it
includes /usr/local/share/lilypond/2.11.64/python, the following line in
make/lilypond-vars.make is supposed to prepend python/out to PYTHONPATH:

export PYTHONPATH:=$(top-build-dir)/python/$(outconfbase):$(PYTHONPATH)

Can you check if this works correctly for you by appending

echo $$PYTHONPATH

to the makefile rule in make/musicxml-rules.make?

Cheers,
John