Same happens on Leopard, but I have not tried the workaround yet
http://trac.macports.org/ticket/18310
yves
Le 09-02-02 à 08:47, Simon Ruderich a écrit :
On Mon, Feb 02, 2009 at 01:20:20AM -0800, Jeremy Huddleston wrote:
Ok, so I played a bit on my Tiger box, and this is a bit odd. As a
workaround for now, you can drop x11/xorg-libXfont to version 1.3.3.
It's weird because if you autoreconf before compiling, this bug is
triggered... which means there's something odd happening in libtool
somewhere... hrm...
Thank you very much, installing xorg-libXfont 1.3.3 worked fine.
X11.app is running now.
But I have another problem. According to top and "Activity
Monitor" X11.bin needs 130-170% cpu all the time. The xterm
window is also sometimes not responsible for 1 to 2 seconds,
after that it gets activated.
With the default X11 binary it worked fine.
Any ideas?
Thanks,
Simon
--
+ privacy is necessary
+ using http://gnupg.org
+ public key id: 0x6115F804EFB33229
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
