Bug#319003: xserver-xorg: Trident and -3: libvgahw is still broken

2005-07-20 Thread Guillaume Melquiond
Le mercredi 20 juillet 2005 à 14:50 +0800, Eugene Konev a écrit : > Can you please test if the problem still exists with the following > libvgahw.a: http://www.imfi.kspu.ru/~ejka/libvgahw.a This version of the library fixes the problem as well. Thanks.

Bug#318405: Bug#319003: xserver-xorg: Trident and -3: libvgahw is still broken, Bug#318405: acknowledged by developer (Bug#318218: fixed in xorg-x11 6.8.2.dfsg.1-3)

2005-07-20 Thread Eugene Konev
Hello David. On Wed, 20 Jul 2005 10:50:28 +0200 you wrote: > What workaround have you tried to build that libvgahw.a? No > optimization, or > an enhanced version of the X.Org patch? Enhanced version. Attached. gcc4 has issues with libvgahw.a. This patch is a workaround stolen from http

Bug#318405: Bug#319003: xserver-xorg: Trident and -3: libvgahw is still broken, Bug#318405: acknowledged by developer (Bug#318218: fixed in xorg-x11 6.8.2.dfsg.1-3)

2005-07-20 Thread Reinhard Karcher
On Wed, Jul 20, 2005 at 02:50:21PM +0800, Eugene Konev wrote > > Can you please test if the problem still exists with the following > libvgahw.a: http://www.imfi.kspu.ru/~ejka/libvgahw.a > Problem doesn't exit anymore. Thank you! Reinhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#319003: xserver-xorg: Trident and -3: libvgahw is still broken, Bug#318405: acknowledged by developer (Bug#318218: fixed in xorg-x11 6.8.2.dfsg.1-3)

2005-07-20 Thread Eugene Konev
Can you please test if the problem still exists with the following libvgahw.a: http://www.imfi.kspu.ru/~ejka/libvgahw.a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#319003: xserver-xorg: Trident and -3: libvgahw is still broken

2005-07-19 Thread Guillaume Melquiond
Package: xserver-xorg Version: 6.8.2.dfsg.1-3 Severity: grave Justification: renders package unusable This bug-report is related to #318218, #318231, #318271, #318405. Feel free to merge it with them. I didn't, because part of the problem reported in these bug-reports was indeed fixed by the las