From: luis jure <ljc@internet.com.uy>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] zlib and WOFF
Date: Mon, 27 Jun 2011 09:21:37 -0300 [thread overview]
Message-ID: <20110627092137.3014e33d@acme7.acmenet> (raw)
In-Reply-To: <9F11097A-F0FD-4DA9-8C9E-6FCA5DAA5D11@stellar.eclipse.co.uk>
on 2011-06-26 at 22:06 Stroller wrote:
>This isn't the best fix, IMO.
i completely agree. by "solution" i meant a quick and dirty fix that
allowed me in the short term to build lilypond.
>IMO the correct fix for this is:
yes, i tried emerging fontforge with the patch you proposed and after that
lilypond compiled OK. thanks!!!
>Finally, report your success at bug 367425.
done.
thank you!
next prev parent reply other threads:[~2011-06-27 12:23 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
2011-06-27 12:21 ` luis jure [this message]
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=20110627092137.3014e33d@acme7.acmenet \
--to=ljc@internet.com.uy \
--cc=gentoo-user@lists.gentoo.org \
/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