*BSD News Article 86055


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 3 problems with FreeBSD 2.1.5 Install
Date: 2 Jan 1997 13:51:46 GMT
Organization: Private BSD site, Dresden
Lines: 35
Message-ID: <5agehi$6fa@uriah.heep.sax.de>
References: <5a9806$ebn@masters0.internex.net>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33493

eric@godzilla.berkeley.edu (Eric van Bezooijen) wrote:

> 1.  Emacs and Xemacs no longer work (I was using FreeBSD 2.1 before), because
> they are missing a library called "libgcc.so.261.0".  I don't see this library
> anywhere on the system, can I get it somewhere ? Why wasn't it installed by
> default ?

Because it's bogus, and got linked into (X)Emacs accidentally.  It's
in the compat20 distribution.  There's no longer a libgcc.so supposed
to be around, so watch out to _not_ drop it into /usr/lib.  Instead,
use /usr/lib/compat/, and run ldconfig on it.

> 2.  When I tried to recompile the kernel to add COM3, I get this error:
> 
> ld: uipc-usrreq.o: read_file_symbols(header): premature EOF
> *** Error code 1

This looks like uipc-usrreq.o is for some obscure reason too short,
but is considered ``up to date'' by make.  Remove it, and run `make'
again.

> 3.  FreeBSD 2.1.5 does not recognize my drive 0.  It's an HP SureStore 2000
> 2.0 GB SCSI drive model C3725S.

On which SCSI controller?  I'm not sure, but there's one HP drive that
is known to not work with tagged commands.  However, the symptoms for
this are usually that the drive is recognized, but the first attempt
to use it crashes with ``Overlapped commands attempted''.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)