Necro bump!
On 8 May 2011, at 02:31, luis jure wrote: > … > for some reason the file /usr/lib64/libz.so is a text file, the solution > was linking it to the real .so file at /lib64/libz.so (or /lib64/libz.so.1 > in my case). after that lilypond builds just fine. This isn't the best fix, IMO. AIUI these bugs have been closed WONTFIX in favour of bug #4411 for years. [1] [2] Seems to me like next time you re-emerge zlib your symlink will get overwritten. You don't give the full error message your original post, but I saw it for myself yesterday (sorry I no longer have it handy) and it is in fact fontforge that gives this error, as it's called during Lilypond's build process. This is now logged as bug 367425 [3], and there is a patch for fontforge there. For the benefit of posterity and anyone else who discovers this bug via google (this is not aimed specifically at Luis), IMO the correct fix for this is: mkdir -p /usr/local/portage/media-gfx/fontforge/files cp /usr/portage/media-gfx/fontforge/fontforge-20110222.ebuild /usr/local/portage/media-gfx/fontforge/ wget https://bugs.gentoo.org/attachment.cgi?id=273709 cp "attachment.cgi?id=273709" /usr/local/portage/media-gfx/fontforge/files/fontforge-20110222-zlib.so.patch Open a text editor add one line to the fontforge-20110222.ebuild you just created in the local overlay: src_prepare() { epatch "${FILESDIR}/${P}-lxkbui.patch" + epatch "${FILESDIR}/${P}-zlib.so.patch" if use doc; then Check your accept keywords for the eBuild, and: ebuild /usr/local/portage/media-gfx/fontforge/fontforge-20110222.ebuild manifest emerge -1 fontforge Finally, report your success at bug 367425. This permits you to test the ebuild for lilypond-2.14.1 at bug 370273. [4] Stroller. [1] https://bugs.gentoo.org/show_bug.cgi?id=4411 [2] https://bugs.gentoo.org/show_bug.cgi?id=290974 [3] https://bugs.gentoo.org/show_bug.cgi?id=367425 [4] https://bugs.gentoo.org/show_bug.cgi?id=370273
