On 01/07/2010 04:24 PM, Jan Nieuwenhuizen wrote: > Op donderdag 07-01-2010 om 16:03 uur [tijdzone +0200], schreef Dave > Plater: > > >> Just had a successful build on line, it fails because of permissions on >> the info dir though, it was either "export GS_LIB="/home/$USER/.fonts" >> or "# norootforbuild" that did it. >> > Then you just may have found a workaround... > > >> As far as your gs bug goes, I get a ghostscript error when I try to view >> the file that causes the failure in mc. >> > ...not sure if it's really helpful though, because with gs 8.70 it > works fine. I think I mentioned that before? ;-) > > I'm attaching the resulting pdf. > > Greetings, > Jan. > > > Well my 11.2 x86_64 home:plater:branches:openSUSE:Factory:Contrib lilypond build has just succeeded, I had to patch out the running of "install-info" in GNUmakefile.in and I'm now close to a finished package. The addition of "export GS_LIB="/home/$USER/.fonts" did the trick for the failure of the doc build, it's lucky that I had it present in my $HOME directory. It must have come from a previous version of suse that I had installed, I haven't cleaned out my home directory since at least 11.0 or maybe even 10.3 and I've updated through factory since 10.3. You are correct that gs shouldn't segfault on a corrupt file or in this case possibly because of the lack of a directory that contains a file called fonts.dir and contains only 0 and a line feed. This would be an upstream bug but upstream will say it's fixed in 8.70. I would appreciate it if you could check my package as I'm not experienced with lilypond before I go any further. The doc build fails on 11.1 ATM but 11.2 and Factory standard succeed, I'll sort out 11.1 at a later stage, I've been neglecting all other work over lilypond. Regards Dave P
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
