public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Simon Stelling <blubb@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] vmware-player fonts unreadable
Date: Sat, 10 Mar 2007 19:56:26 +0100	[thread overview]
Message-ID: <45F2FF5A.1070608@gentoo.org> (raw)
In-Reply-To: <20070308235742.GA13331@brego.pewamo.office>

Michael George wrote:
> Has anyone else run into this?  Is it perhaps the emulation libraries
> being a problem?

Most certainly. Though for most people experiencing font problems after
upgrading the emul-packages, this only lead to "blurry fonts". The
problem is that we're distributing a 32bit copy of freetype in
emul-linux-x86-xlibs. As it's binary, we have to use USE=bindist to
avoid legal problems. Unfortunately that means that some dll-loading
code is replaced with some other code, which is why the fonts suddenly
look different.

https://bugs.gentoo.org/show_bug.cgi?id=167632

As for the solution: You can a) build your own freetype [1] or b)
convince me that we won't run into legal problems when distributing a
USE=-bindist freetype :)

[1] See http://amd64.gentoo.org/emul for some hints


-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64
-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2007-03-10 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 23:57 [gentoo-amd64] vmware-player fonts unreadable Michael George
2007-03-09  1:36 ` Chris Traylor
2007-03-09 14:50 ` The Doctor
2007-03-10 14:04   ` Michael George
2007-03-10 14:36     ` Michael George
2007-03-10 14:47       ` Joe Menola
2007-03-10 15:00         ` Michael George
2007-03-10 15:24           ` Joe Menola
2007-03-10 15:51             ` Nuitari
2007-03-10 18:38             ` Michael George
2007-03-10 18:39             ` Michael George
2007-03-10 18:46               ` Joe Menola
2007-03-10 19:05               ` Richard Freeman
2007-03-10 19:29                 ` Michael George
2007-03-10 18:56 ` Simon Stelling [this message]
2007-03-12 13:18 ` The Doctor
2007-03-12 16:31   ` Cermelo Woodgett

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=45F2FF5A.1070608@gentoo.org \
    --to=blubb@gentoo.org \
    --cc=gentoo-amd64@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