From owner-freebsd-questions Mon Nov 25 13:39:22 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11598 for questions-outgoing; Mon, 25 Nov 1996 13:39:22 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11577 for ; Mon, 25 Nov 1996 13:38:53 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.3/8.6.12) with SMTP id NAA01446; Mon, 25 Nov 1996 13:39:59 -0800 (PST) Date: Mon, 25 Nov 1996 13:39:58 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: MDM cc: FreeBSD Support Subject: Re: ld.so and emacs problems In-Reply-To: <53961120211735/0006695923PK1EM@MCIMAIL.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 20 Nov 1996, MDM wrote: > I have completed installing FreeBSD 4.4-Lite from the Walnut Creek 2.1.5 > CD-Rom; there are three problems that I need some help with. The proper version number is FreeBSD 2.1.5-RELEASE. You should consider returning this CD and picking up 2.1.6 after it comes out. > 1. EMACS 19.31 will not "start". I get an error message: > ld.so failed: Can't find shared library "libgcc.so.261.0" > I have searched for this file and have found: > /usr/lib/libgcc.a, libgcc_pic.a, libgcc_p.a > /usr/local/lib/libgcc.a > /usr/src/gnu/usr.bin/cc/libgcc/libgcc1.c, libgcc2.c Hm, I see a /usr/lib/libgcc.so.261.0. If you're missing it for some reason you can grab mine: ftp://gdi.uoregon.edu/pub/libgcc.so.261.0.gz > 2. What command generates the locate database > /var/db/locate.database ? > The locate man page doesn't tell. Just leave the machine on Friday night, or grab the command line from /etc/weekly. > 3. I "chsh"ed the root shell to Bash (and also of my normal account), but > paths and aliases written in the either the /root/.bashrc ( or the > /usr/home/myhome/.bashrc) do not get "accessed" or read or "used". What's > up? I'm not familiar with Bash, but since it's based on sh I would say it's picking up the .profile in /root and ignoring your .bashrc. The bash man page should show which file(s) it wants. I would HIGHLY recommend changing root back to sh; you won't be able to log in if your /usr partition disappears, while a static version of sh is in /bin. You should use su instead of logging in as root. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major