From owner-freebsd-questions Sun Aug 30 17:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24642 for freebsd-questions-outgoing; Sun, 30 Aug 1998 17:02:50 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from netbox.com (home.netbox.com [206.24.105.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24635 for ; Sun, 30 Aug 1998 17:02:48 -0700 (PDT) (envelope-from jwgray@netbox.com) Received: from localhost (jwgray@localhost) by netbox.com (8.8.8/8.8.7) with SMTP id RAA03686; Sun, 30 Aug 1998 17:02:20 -0700 (PDT) (envelope-from jwgray@netbox.com) Date: Sun, 30 Aug 1998 17:02:20 -0700 (PDT) From: Jeff Gray To: questions@FreeBSD.ORG cc: Jeff Gray Subject: StarOffice 3.1 Install seems to have done some damage.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG StarOffice 3.1 Install seems to have done some damage.... Not at all clear what happened here or how to fix it. Running 2.2.6 - happily with no difficulties. For 'fun' thought I would install StarOffice 3.1 Have been using emacs etc. with no problems. downloaded the staroffice.tar and did the install. Realized that I had not enabled linux in /etc/rc.conf No biggie [btw: do you have to reboot after modifying /etc/rc.conf? ] from root cm110119# emacs /etc/rc.conf ld.so failed: Can't find shared library "libXaw.so.6.1" cm110119# emacs ld.so failed: Can't find shared library "libXaw.so.6.1" then tried pico cm110119# pico ld.so failed: Can't find shared library "libpico.so.1.3" But it is clearly still there. cm110119# locate libXaw.so.6.1 /usr/X11R6/lib/libXaw.so.6.1 cm110119# ls -l /usr/X11R6/lib/libXaw.so.6.1 -rw-r--r-- 1 root wheel 244951 Mar 1 1998 /usr/X11R6/lib/libXaw.so.6.1 I can no longer open any editor. Or even pine. Strange, but elm works as a reader but I cannot seem to edit. Yikes. Thanks Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message