https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #118 from Kevin Brace <kevinbr...@gmx.com> --- (In reply to Mario Rugiero from comment #117) Hi Mario, > Just a thought, but if VBE doesn't play well on 64 bits, why not keep it > there for 32 bits? Only if it actually adds any value compared to the > alternative, of course. Personally, I do not like anything like VBE, but the way I see is, for historical reasons, it is there. I will like to get rid of it, but I am sure some will be opposed. Although I am probably not enough of an expert to debate the merits, I will be in the camp of not wanting to get rid of XAA code base, if that was possible. This is because there might be someone that might want to compile OpenChrome for old xorg. Off topic, but I have tried to compile the current OpenChrome code base for Ubuntu 8.04 LTS, and after some try, I did manage to find a way to somehow compile it. The reason I say it like this is because I had to fix some code in xorg header files in order for the compilation to go through. To my surprise, it does work, but unfortunately, the top GNOME task bar gets corrupted very quickly (obviously this is a bug), so it is not perfect at all. The current code base does require some changes that I will eventually commit as a patch for the compilation to go through without too much manual code editing. This will not happen for a while since it is not a super important issue to work on. Regards, Kevin Brace -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/openchrome-devel