From owner-freebsd-current Tue May 30 14:32:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA29726 for current-outgoing; Tue, 30 May 1995 14:32:47 -0700 Received: from crystal.PEAK.ORG (root@crystal.PEAK.ORG [198.68.23.56]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA29685 for ; Tue, 30 May 1995 14:32:42 -0700 Received: from lostlhost (careya@localhost [127.0.0.1]) by crystal.PEAK.ORG (8.6.9/8.6.4) with ESMTP id OAA12187; Tue, 30 May 1995 14:32:32 -0700 Message-Id: <199505302132.OAA12187@crystal.PEAK.ORG> X-Mailer: exmh version 1.6 4/21/95 To: Peter Dufault cc: current@FreeBSD.ORG Subject: Re: ld.so: xterm: libXaw.so.6.0: Undefined error: 0 In-reply-to: Your message of Tue, 30 May 1995 15:06:40 -0400. <199505301906.PAA00694@hda.com> X-URI: http://www.peak.org/~careya Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 May 1995 14:32:21 -0700 From: Andrew Carey Sender: current-owner@FreeBSD.ORG Precedence: bulk Peter Dufault wrote: > We have three systems in house running the same current, built from > a successful "build world" of a few days ago, and one of them gets > the error: > > "ld.so: xterm: libXaw.so.6.0: Undefined error 0" > > when you run most X apps. I've torn my hair out trying to figure > out what is going on. I've had this happen as well. It turned out that the shared libs for X weren't being added to the shared library cache with ldconfig at boot. Look for the line starting with ldconfig in your rc.local, and add the location of your X libs to the end. On my machine this line looks like: ldconfig /usr/lib /usr/local/lib /usr/local/gnu/lib /usr/local/X11R5/lib This is on a hp300 running NetBSD 1.0, though, so your mileage may vary. Andy Carey, KSC | Public Terminal/HP Support | careya@peak.org Semper Ubi Sub Ubi | "The gostak distims the doshes" | SPLF/cor