[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gub: I can now completely build lilypond

From: Knut Petersen
Subject: Re: gub: I can now completely build lilypond
Date: Thu, 17 Jan 2019 13:46:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

Hi Werner!
But building of lilypond-test fails.


    /home/gub/NewGub/gub/target/tools/root/usr/bin/texi2dvi: texinfo.tex
    appears to be broken.
    This may be due to the environment variable TEX set to something
    other than (plain) tex, a corrupt texinfo.tex file, or
    to tex itself simply not working.
    version `CXXABI_1.3.9' not found (required by etex)
Obviously another linking path issue: While executing the external TeX
binaries, DLL stuff from `target/...' must not be used.

The problem here is that our texi2* stuff needs LD_LIBRARY_PATH to find our 
DLLs in target/..., but the system's etex binary, executed by texi2*, fails on 
openSuSE Tumbleweed because it is incompatible to those libs in target/....

I think the easiest solution is a simple etex wrapper script in tools/root that 
clears LD_LIBRARY_PATH and then executes the system's etex.

With the three patches attached on top of the waiting gub pull requests

   rm -rf target
   make lilypond
   make LILYPOND_BRANCH=stable/2.20 lilypond
   make LILYPOND_BRANCH=release/unstable lilypond

all succeed on openSuSE Tumbleweed.

ubuntu 18 is still broken, and the 0001-Fix... patch ignores that it breaks gub 
on all systems that don't have a gcc-7. Obviously some polishing is needed, but 
first I will spend some time on fixing the issues on ubuntu 18.


Attachment: 0001-Fix-building-python-on-openSuSE-tumbleweed.patch
Description: Text Data

Attachment: 0002-Install-db-libs-in-usr-lib-as-well-as-usr-lib64.patch
Description: Text Data

Attachment: 0003-Fix-lilypond-test.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]