*BSD News Article 85831


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in3.uu.net!140.174.88.1!wsrcc.com!not-for-mail
From: wolfgang@wsrcc.com (Wolfgang Rupprecht)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: LD_LIBRARY_PATH and XFree86 3.2 on NetBSD/i386
Date: 30 Dec 1996 15:06:11 -0800
Organization: W S Rupprecht Computer Consulting, Fremont CA
Lines: 17
Message-ID: <5a9ht3$sn6@wsrcc.com>
NNTP-Posting-Host: wsrcc.com
Summary: is LD_LIBRARY_PATH needed for XFree86 3.2 (X11R6.1)
Keywords: LD_LIBRARY_PATH
X-Newsreader: NN version 6.5.0 #5 (NOV)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:5034

I'm trying to get XFree86 3.2 up on virgin NetBSD/i386 system.  It
apears that the LD_LIBRARY_PATH must be set or ldconfig must include
the X-libs for the apps to function correctly.

In the SunOS way of handling this, one could link an absolute path
into the executable and have the run-time linker look for the
libraries with those absolute names.  This allowed one to have a bit
of overlap when, for example, upgrading the X11 tree.  The old
executables would still use the old lib path and the new executables
could use the new lib path.

Is there a similar way to do this under NetBSD?

-wolfgang
-- 
Wolfgang Rupprecht    <wolfgang@wsrcc.com>     <http://www.wsrcc.com/> 
          Sick of email spam?  <http://www.vix.com/spam/>