On Thu, Mar 29, 2012 at 3:04 AM, Colin Hall <colingh...@gmail.com> wrote:
> > > On Wed, Mar 28, 2012 at 04:40:34PM -0700, Joe Neeman wrote: > > Consider the following lilypond-book output (version 2.14.2): > > lilypond-book --pdf --latex-program=xelatex -o out miriam.lytex > > lilypond-book (GNU LilyPond) 2.14.2 > > Reading miriam.lytex... > > Running xelatex...xelatex: /home/jneeman/lilypond/usr/lib/libstdc++.so.6: > > no version information available (required by xelatex) > > ... > > xelatex: relocation error: xelatex: symbol > > _ZNSt8__detail15_List_node_base7_M_hookEPS0_, version GLIBCXX_3.4.15 not > > defined in file libstdc++.so.6 with link time reference > > command failed: xelatex /tmp/tmpPBb_rA.tex > > Child returned 127 > > > > It looks like lilypond-book is running xelatex in a modified environment > > (eg. with LD_LIBRARY_PATH set). Since xelatex is not packaged with > > lilypond, it should be linked against whatever libraries are present on > the > > system, not the libraries that are packaged with lilypond. > > Thanks for reporting this, Joe. > > I just had a look at the lilypond-book code. It looks to me like the > TeX processing program is launched with a copy of the current > environment. As you probably know, the lilypond binary is launched via > a wrapper script that sets LD_LIBRARY_PATH so yes, the environment for > xelatex is > modified and not the same as the one established by your shell. > > I suspect the designers considered it the user's resposibility to > supply an alternative TeX processor that can cope with the lilypond > runtime environment. > If this is indeed intentional, I think the intention is wrong. Since we don't package TeX, we know that we are using the system TeX, and so it should be launched with the system environment. > > For a workaround I did some research and found this posting on > lilypond-user: > > http://lists.gnu.org/archive/html/lilypond-user/2010-03/msg00055.html > > in which Joseph Wakeling suggests a workaround of running xelatex on > the TeX source produced by the failed run of lilypond book. Let us > know if that works for you. > I need to run xelatex on the produced source anyway, since lilypond-book doesn't do that for me. However, this doesn't provide a workaround: lilypond-book needs to successfully run xelatex in order to determine the line width for producing the snippets. > Has xelatex ever worked for you? > > Have you updated xelatex or lilypond recently? > Yes, xelatex by itself works fine. Lilypond-book works fine with xelatex if I compile it from git (which is what I usually do). It fails when I install the prebuilt packages (tested with 2.14 and 2.15). By the way, this is not specific to xelatex; I have the same problem with normal latex, but it happened that the file I was working on last week needed xelatex. Could you create a wrapper script for xelatex to establish the > environment it needs? Presumably. For my personal use, I can just compile lilypond from git and then it just works. I really just reported it because I think that it's a bug and I thought it might eventually affect someone else. Cheers, Joe _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
