From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Cc: luis jure <ljc@internet.com.uy>
Subject: Re: [gentoo-user] zlib and WOFF
Date: Sun, 26 Jun 2011 22:06:48 +0100 [thread overview]
Message-ID: <9F11097A-F0FD-4DA9-8C9E-6FCA5DAA5D11@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20110507223153.38acacb5@acme7.acmenet>
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
next prev parent reply other threads:[~2011-06-26 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 4:07 [gentoo-user] zlib and WOFF luis jure
2011-04-24 4:31 ` Adam Carter
2011-04-24 11:28 ` luis jure
2011-04-24 11:48 ` Volker Armin Hemmann
2011-04-24 13:27 ` luis jure
2011-04-24 12:06 ` Stroller
2011-05-07 10:58 ` Enrico Weigelt
2011-05-08 1:31 ` luis jure
2011-06-26 21:06 ` Stroller [this message]
2011-06-27 12:21 ` luis jure
2011-06-27 19:17 ` Stroller
2011-06-28 23:31 ` luis jure
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9F11097A-F0FD-4DA9-8C9E-6FCA5DAA5D11@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
--cc=ljc@internet.com.uy \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox