A quick update: a newly compiled sc executable works. Perhaps
there should have been a major number increase, or maybe the
__RENAME() hack.

					Gary D. Duzan



In Message <199905292124.RAA22623@wheel.tiac.net> ,
   Gary Duzan <gary@wheel.tiac.net> wrote:

=>
=>   I have an old "sc" executable which is behaving strangely after
=>upgrading to 1.4C:
=>
=>wheel { ~ } % uname -a
=>NetBSD wheel 1.4C NetBSD 1.4C (WHEEL) #0: Sat May 29 09:14:26 EDT 1999     ga
ry@wheel:/disk1/src/sys/arch/i386/compile/WHEEL i386
=>wheel { ~ } % ident `which sc`
=>/usr/local/bin/sc:
=>     $NetBSD: crt0.c,v 1.28 1997/10/20 13:49:45 mycroft Exp $
=>     $NetBSD: skeleton.c,v 1.14 1997/10/20 03:41:16 lukem Exp $
=>     $Revision: 6.21 $
=>     $NetBSD: regex.c,v 1.7 1997/10/09 10:20:51 lukem Exp $
=>     $NetBSD: regexp.c,v 1.7 1997/10/09 10:21:18 lukem Exp $
=>wheel { ~ } % ldd `which sc`
=>/usr/local/bin/sc:
=>        -lm.0 => /usr/lib/libm.so.0.1 (0x40037000)
=>        -lcurses.2 => /usr/lib/libcurses.so.2.5 (0x40050000)
=>        -ltermcap.0 => /usr/lib/libtermcap.so.0.0 (0x4005e000)
=>        -lc.12 => /usr/lib/libc.so.12.41 (0x40060000)
=>wheel { ~ } % 
=>
=>When I bring up an old spreadsheet I get junk (like "1`5`") in the
=>current cell, and similar junk as I move around the screen. I get
=>similar results from an xterm, wscons/vt100, or screen.
=>   Also, it was a pain trying to get the build to complete as I
=>kept getting "Cannot fork" errors at random places during the build.
=>Once I managed to get everything installed it seemed to clear up,
=>though so maybe I just needed a new "make" executable.
=>
=>					Gary D. Duzan
=>
=>