From owner-freebsd-ports Mon May 11 13:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17625 for freebsd-ports-outgoing; Mon, 11 May 1998 13:52:02 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from parsons.rh.rit.edu (root@d117-h041.rh.rit.edu [129.21.117.169]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA17578 for ; Mon, 11 May 1998 13:51:58 -0700 (PDT) (envelope-from mfisher@harborcom.net) Received: from mfisher by parsons.rh.rit.edu with smtp (Exim 1.82 #1) id 0yYzXt-0000sQ-00; Mon, 11 May 1998 16:51:37 -0400 Date: Mon, 11 May 1998 16:51:37 -0400 (EDT) From: Mike Fisher X-Sender: mfisher@d117-h041.rh.rit.edu To: freebsd-ports@FreeBSD.ORG Subject: xscreensaver problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After updating the Xaw libraries per the security warning with the FreeBSD binaries at ftp://ftp.xfree86.org/pub/XFree86/3.3.2/binaries/FreeBSD-2.2.x/X3321upd.tgz the xscreensaver will not work properly. The screensaver died every time it became active with an error message that it had received SIGSEGV. An attempt to rebuild xscreensaver dies with the errors: cc -L/usr/X11R6/lib -o xscreensaver demo.o stderr.o subprocs.o timers.o windows.o xscreensaver.o xset.o dialogs-Xaw.o lock.o kpasswd.o ../utils/fade.o ../utils/overlay.o ../utils/resources.o ../utils/usleep.o ../utils/visual.o ../utils/xroger.o ../utils/spline.o ../utils/yarandom.o -L/usr/X11R6/lib -lXaw -lXmu -lXss -lXt -lSM -lICE -lX11 -lXext -lkrb -ldes -lnsl -lsocket -lcrypt ld: -lnsl: no match *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thank you. -- Mike "I swear - by my life and by my love of it - that I will never live for the sake of another man, nor ask another man to live for mine." --Ayn Rand, _Atlas Shrugged_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message