Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!hpg30a.csc.cuhk.hk!news.hk.net!howland.reston.ans.net!math.ohio-state.edu!news.acns.nwu.edu!uicvm.uic.edu!news.eecs.uic.edu!not-for-mail
From: jscholvi@ernie.eecs.uic.edu (John Scholvin)
Newsgroups: comp.os.386bsd.questions
Subject: FreeBSD packages might need updating for XFree86 3.1
Date: 5 Oct 1994 18:01:24 -0500
Organization: University of Illinois at Chicago
Lines: 33
Message-ID: <36vb84$adv@ernie.eecs.uic.edu>
NNTP-Posting-Host: ernie.eecs.uic.edu
I've grabbed XFree86 3.1 and (finally) got X working with FreeBSD! Happy day!
Thanks to everyone responsible--the new configuration stuff is really cool.
I think I've found trouble, though. When grabbing the binary packages from
freebsd.cdrom.com, a lot of them seem to want version 2.0 of the various
shared libraries, and the version shipped with XFree86 3.1 are 6.0.
For example: after grabbing and installing (with pkg_add) axe_bin.tgz from
freebsd.cdrom.com, I get the following error when I try to run it:
ld.so: axe: libXaw.so.2.0: No such file or directory
Please forgive me if I have my terminology confused here, I'm still new to
this stuff! Anyway, the only attempt I made at fixing this was using sym
links from the various 2.0 file names to the 6.0 files, and for my efforts I
get core dumps. Obviously, a naive attempt, but all I know right now.
So, do I need to wait for the charity of those who put those packages out
there, or is there something simple I can do? Recompiling from source is a
less than ideal option due to limited disk space and the fact that I can
never seem to build X source packages I grab off the net. Help! And then I
promise I'll quit littering the net with my trivial questions.
Thanks...
--
John Scholvin | "Help--I've fallen into a depression in
jscholvi@eecs.uic.edu | the space-time continuum and I can't get
| up!" -- K. Gleason