Re: Jade DONE and working!
On Tue 10 Nov 1998, Christopher C Chimelis wrote:
> locations and names). To compound the issue, "sp" never completely
> removed on my system (take note of this...since it'll probably happen to
> everyone). What I ended up doing was forcibly removing the "jade" and
> "sp" packages (using --purge --force-depends), then check /usr/lib for
> ANYTHING related to libsp (it had left the .so link behind linked to the
> libsp.so.1.3.old that it also renamed and left) and delete any such lib
> manually. Once you are confident that both packages are totally removed,
> then install the new jade, sp, and libsp* packages.
Hmmm, couldn't this be handled in the preinst script of the new
package? It seems that the "new" preinst script is always run.
This could save a lot of folks a lot of pain...
> Whew...now THAT is a load off of my mind. I would encourage everyone who
> encountered optimiser problems to try the new egcs. So far, I haven't run
> into any problems, but I may not be hitting the difficult cases yet.
This is the gcc_2.91.58-3_alpha.deb that's currently in Incoming,
right? Could you also try a new libc with this compiler (see my
fscanf problem, I posted this on Monday). I'd do it, but seeing
how you're up to speed on this... :-)
Paul Slootman
--
home: paul@wurtel.demon.nl | work: paul@murphy.nl | debian: paul@debian.org
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Reply to: