Hi. > > $ sh lilypond-2.6.3.1.x86.package > > /usr/libexec/autopackage/autosu-gtk: error while loading shared libraries: > > libgtk-x11-2.0.so.0: cannot open shared object file: No such file or > > directory > > looks like an autopackage error. It seems you have autopackage > installed on your system, can you try what happens if you remove > autopackage? The lilypond install command should still work, > it has autopackage on board. >
After cleaning up "autopackage", and reinstalling: # Preparing: LilyPond # Checking for required C library versions ... failed # FAIL: # Your copy of glibc, a core system library, is too old for this package. # You need at least the following symbols in glibc: GLIBC_2.0. # # This error normally means that whoever built the package did not build it correctly. # Please report the contents of this message to the provider of this package, and # ask them to rebuild it using apbuild. # # Upgrading glibc is highly dangerous, so we recommend in this situation that you # compile the app you want to install from the sources if possible. Sorry :( FAIL: Unable to prepare package LilyPond. > > I'd prefer installing through the Debian management system, but no new > > version is provided on the web site :-( > > Yes, that's very sad. LilyPond's dependencies in Debian have been > stalled for quite some time. > [...] > > > It seems that the documentation is causing the problem... > > Yes. > So, I commented out the "build-doc" prerequisite from the "binary-indep" target in the "rules" Makefile, and now the error is: /usr/bin/make --no-builtin-rules final-install make[2]: Entering directory `/home/eran/tmp/music/lilypond/build/lilypond-2.6.3' make[2]: Leaving directory `/home/eran/tmp/music/lilypond/build/lilypond-2.6.3' make[1]: Leaving directory `/home/eran/tmp/music/lilypond/build/lilypond-2.6.3' dh_install --sourcedir=debian/tmp --list-missing cp: cannot stat `debian/tmp/usr/lib': No such file or directory dh_install: command returned error code 256 make: *** [install] Error 1 > > Does someone still maintain the debian packages? > > Only for the regular Debian releases, but Debian is still at 2.4, as > 2.6 does not yet build because of missing dependencies. > Yes, 2.4.5 (which I currently use) is the latest on Debian. But what are the missing dependencies? (Is there some document that states all the problems?) > > I would be willing to help if necessary (although currently, > > I know very little about deb packaging). Is it necessary? Best regards, Gilles _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
