Re: [Denemo-devel] Failure to run LilyPond was Re: The 1.0 release

[Richard Shann]

On Thu, 2013-01-24 at 10:19 +0000, Richard Shann wrote:
> Pango-WARNING
> **: /home/rshann/denemo/usr//lib/pango/1.6.0/modules/pango-basic-fc.so:
> wrong ELF class: ELFCLASS32
> 
> Now as I have a 64 bit machine this is not surprising by iteself, but 
> 
> a) Why does it not happen when the same script is invoked from the
> dynamically build Denemo 
> b) I thought you have the same problem on a 32-bit machine - can you
> confirm/deny this. That is, does your statically built linux denemo
> run
> lilypond ok or not? 

What I was glossing over here is that the LilyPond executable is finding
pango in the denemo installation.
So the environment variables created in ~/.denemo.env by the denemo
startup script have to be changed for the lilypond run.
Even doing this does not quite get there because although LilyPond runs
correctly evince has a similar problem.
That is I set these
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
INSTALLER_PREFIX=/home/rshann/lilypond/usr
if test -d /home/rshann/lilypond/usr/lib/gtk-2.0/2.10.0/loaders; then
    export GIO_MODULE_DIR=/home/rshann/lilypond/usr/lib/gio/modules
    export
GDK_PIXBUF_MODULEDIR=/home/rshann/lilypond/usr/lib/gtk-2.0/2.10.0/loaders
##    export
GDK_PIXBUF_MODULE_FILE=/home/rshann/lilypond/usr/etc/gtk-2.0/gdk-pixbuf.loaders
    export GTK_DATA_PREFIX=/home/rshann/lilypond/usr/lib/gtk-2.0
    export GTK_EXE_PREFIX=/home/rshann/lilypond/usr
    export
GTK_IM_MODULE_FILE=/home/rshann/lilypond/usr/etc/gtk-2.0/gtk.immodules
    export GTK_PATH=/home/rshann/lilypond/usr/lib/gtk-2.0
    export GTK_SYSCONFDIR=/home/rshann/lilypond/usr/etc
fi
export LD_LIBRARY_PATH="/home/rshann/lilypond/usr/lib"
export FONTCONFIG_FILE=$INSTALLER_PREFIX/etc/fonts/fonts.conf
export FONTCONFIG_PATH=$INSTALLER_PREFIX/etc/fonts
export GS_FONTPATH=$INSTALLER_PREFIX/share/ghostscript/8.70/fonts:
$GS_FONTPATH
export GS_FONTPATH=$INSTALLER_PREFIX/share/gs/fonts:$GS_FONTPATH
export GS_LIB=$INSTALLER_PREFIX/share/ghostscript/8.70/Resource:$GS_LIB
export GS_LIB=$INSTALLER_PREFIX/share/ghostscript/8.70/Resource/Init:
$GS_LIB
export GTK_PREFIX=$INSTALLER_PREFIX
export GTK_MODULE_VERSION=2.10.0
export GTK_SO_EXTENSION=.so
export GUILE_LOAD_PATH=$INSTALLER_PREFIX/share/guile/1.8:
$GUILE_LOAD_PATH
export PANGO_RC_FILE=$INSTALLER_PREFIX/etc/pango/pangorc
export PANGO_PREFIX=$INSTALLER_PREFIX/
export PANGO_MODULE_VERSION=1.6.0
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
in the ~/bin/lilypond script before it launches the lilypond executable
and lilypond launches ok and generates the correct pdf but evince
complains:

(denemo:29235): EvinceDocument-WARNING
**: /usr/lib/evince/2/backends/libpdfdocument.so: wrong ELF class:
ELFCLASS64

So the evince library is not getting its libpdfdocument.so from the
local ~/denemo/usr/lib (it is not there, there are other evince
libraries e.g. libevdocument.so in there...)

I am not sure of the best way forward though ... should we be creating a
single installer that has both lilypond and denemo in the same bin, with
only one /usr for both? And it does look like evince is depending on
some system installed libraries...

Richard