Re: Whereis lilylib etc. - Build system - Python modules

[Colin Campbell]

On 11-06-26 01:08 AM, Villum Sejersen wrote:
> Hello
> For several years I have been compiling the lilypond master branch.
> Today’s result is strange: LilyPond compiles and installs as it 
> should, but all the python modules throw an error when called.
>
> The error shown below on loading modules also was present for a few 
> days during the 2.13 development series, but apparently accidentally 
> solved without being recognized as a bug.
>
>
>
> address@hidden:/usr/local/src/lilypond# uname -a
> Linux Villums12 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 
> x86_64 GNU/Linux
>
> address@hidden:/usr/local/src/lilypond# python --version
> Python 2.6.6
>
> address@hidden:/usr/local/src/lilypond# gcc --version
> gcc (Debian 4.4.5-8) 4.4.5
> Copyright (C) 2010 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
> PURPOSE.
>
> address@hidden:/usr/local/src/lilypond# date
> sun jun 26 08:38:34 CEST 2011
>
> address@hidden:/usr/local/src/lilypond# git pull origin
> Already up-to-date.
>
> *** at this point Lilypond was compiled and installed ***
>
> address@hidden:/usr/local/src/lilypond# lilypond --version
> GNU LilyPond 2.15.3
>
> Copyright (c) 1996--2011 by
> Han-Wen Nienhuys <address@hidden>
> Jan Nieuwenhuizen <address@hidden>
> and others.
>
> This program is free software. It is covered by the GNU General Public
> License and you are welcome to change it and/or distribute copies of it
> under certain conditions. Invoke as `lilypond --warranty' for more
> information.
>
> address@hidden:/usr/local/src/lilypond# convert-ly --version
> Traceback (most recent call last):
> File "/usr/local/bin/convert-ly", line 51, in <module>
> import lilylib as ly
> ImportError: No module named lilylib
>
> *** The old version (debian package) works as expected: ***
>
> address@hidden:/usr/local/src/lilypond# /usr/bin/convert-ly --version
> 2.12.3
>
> address@hidden:/usr/local/src/lilypond# whereis convert-ly
> convert-ly: /usr/bin/convert-ly /usr/local/bin/convert-ly 
> /usr/share/man/man1/convert-ly.1.gz
>
> address@hidden:/usr/local/src/lilypond# musicxml2ly --version
> Traceback (most recent call last):
> File "/usr/local/bin/musicxml2ly", line 35, in <module>
> import lilylib as ly
> ImportError: No module named lilylib
>
> address@hidden:/usr/local/src/lilypond# abc2ly --version
> Traceback (most recent call last):
> File "/usr/local/bin/abc2ly", line 121, in <module>
> import lilylib as ly
> ImportError: No module named lilylib
> address@hidden:/usr/local/src/lilypond#
>
>
> Anyone?


Just at a guess: it looks as though you are installing as root, and 
using /usr/local/src as your toplevel directory.  You also have two 
versions of convert-ly, for example: one in /usr/bin and the other in 
/usr/local/bin and your problems are coming from the mixup between 
relative and absolute paths.The recommended method is to use the 
lily-git.tcl script to create and update a source tree in your home 
folder.  This avoids the need to install as root, and makes it easier to 
avoid path issues.

Because the instructions for installing lilypond are quite definite 
about it belonging in the home folder, this really can't be considered a 
bug.  My best recommendation, for compiling git master, would be to 
start here <cid:part1.06060605.07030509@shaw.ca>, and consider helping 
out with the Frogs or Bug Squad ;>.

Colin Campbell
Bug Squad

--
The human race has one really effective weapon, and that is laughter.
-- Mark Twain