From: Dr. Michael Weller (eowmob@exp-math.uni-essen.de)
Date: Fri 17 Jul 1998 - 15:54:54 IDT
On Fri, 17 Jul 1998 michael_diack_at_gbvaonc2@ukos.varian.com wrote: > is remove existing svgalib support, so I'm now left with a machine > that can't run any svgalib appilcations without seg faulting. > Reinstalling svgalib via RPM does not cure the problem, so I will > reinstall Linux from scratch. Hmm.. reinstalling the old version should work of course. Maybe, in the unpacked directory of 1.3.0, try "make uninstall" it should remove ANY, even the smallest, trace of svgalib, s.t. you can reinstall the RPM version. Also, the rpm package might think that it the old version is still installed. I know it has a force option to force reinstall, but I don't know the exact flags (I don't have an RPM based system). Otherwise you could get a plain (not RPM) svgalib-1.2.13 and install it instead. I won't reinstall linux from scratch in your position. That's too much work and there'll be easier ways to help you. > Two questions: > 1) Is a patch/fix forthcoming? Yep. I'm working on this already. > 2) Could you adjust the make process so that it doesn't disable any > existing svgalib support until the build process has completed OK? Not that easily, as the old, still installed, version will hinder compilation of utilities and demos. It should be possible to keep the old libs though. Actually, I'm pretty sure there is an option already not to remove existing share library images. Just enable it in the Makefile.cfg. Anyway.. I've to work on it a bit more on the next days, I'll see what I can do. A bit more detail: The actual problem lies in certain weird kernel dependencies of the (partial) VESA support. Plus, although svgalib in general works well with glibc, the new lrmi.c code has the weirdest problems when compiled with glibc (which I unfortunetaly couldn't test myself). As a quick fix, just do not include the VESA driver in Makefile.cfg (as it is the default), that should make it compile nicely. Michael. -- Michael Weller: eowmob@exp-math.uni-essen.de, eowmob@ms.exp-math.uni-essen.de, or even mat42b@spi.power.uni-essen.de. If you encounter an eowmob account on any machine in the net, it's very likely it's me.
This archive was generated by hypermail 2.1.4 : Wed 21 Jan 2004 - 22:10:22 IST