Date: Fri, 29 Jul 2005 12:53:29 -0700 From: Brandon Fosdick <bfoz@bfoz.net> To: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= <bkoenig@cs.tu-berlin.de> Cc: ports@freebsd.org, olgeni@freebsd.org Subject: Re: Eterm transparency/shading problem Message-ID: <42EA8939.107@bfoz.net> In-Reply-To: <42EA8696.8020307@cs.tu-berlin.de> References: <42EA7048.7050006@bfoz.net> <42EA8696.8020307@cs.tu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah, that makes sense. I usually compile Eterm with MMX enabled but somehow forgot this time. Now it looks much better. Would it be worthwhile to make this compile option part of that new(?) options framework that some of the ports seem to be using? Thanks for the reply. Björn König wrote: > Brandon Fosdick wrote: > >> I just cvsup'd ports the other day and rebuilt Eterm, now the >> transparency/shading option tints everything blue, regardless of the >> actual settings. Previously I had "cmod 160" and it made the >> background about %50 shaded, as expected. Any idea what happened, or >> how to fix this? >> >> Apparently I'm not the only one with this problem, but I don't see any >> responses. >> http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/078221.html > > > > This is a bug in Eterm and it has been fixed in the upcoming next > release of Eterm. > > To solve this problem now you either need to compile it with MMX > support, e.g. > > make -DWITH_MMX install clean > > or in case your machine has no support for MMX put the quick patch that > I attached to this mail into /usr/ports/x11/eterm/files/ and build Eterm > as usual.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42EA8939.107>