Date: Tue, 8 Jun 2004 13:13:12 -0700 (Pacific Daylight Time) From: Andrew Carter <andrewc@blarg.net> To: Christopher Nehren <apeiron@comcast.net> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: Subversion 1.0.4 install problem Message-ID: <Pine.WNT.4.60.0406081310090.3576@ACARTERM1.redmond.corp.microsoft.com> In-Reply-To: <20040608181840.GA79388@prophecy.dyndns.org> References: <Pine.OSX.4.58.0406071224020.21070@whistler.local> <20040608181840.GA79388@prophecy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Jun 2004, Christopher Nehren wrote: > > The problem is that, for some reason, /usr/local/lib/apache2 isn't in > your library search path. I've solved this by doing: > > ldconfig -m /usr/local/lib/apache2 > > It's important that you use the -m flag: otherwise, all of your existing > library search paths will be erased, and you'll be very lucky to fix > them again. > > I've seen this problem on two machines, but am not exactly sure of how > to fix it. My guess is that it's something with www/apache2, but it's > very likely that I'm wrong. > >> I created symbolic links (ln -s) for the two libapr* shared libraries in >> /usr/local/lib and it appears to work. Anyone know what's going on here? > > Don't *ever* use symbolic links to resolve library issues. *EVER*. It > will only dig you into a hole that may one day become impossible to > escape. This might be a flippant reaction, but I speak from experience. > In fact, once you do the ldconfig command, it may be wise to remove > those symlinks just to be safe. Subversion will still work, because the > linker (at least AFAIK) searches by library name, not by hardcoded > paths. If it doesn't, you'll have to reinstall. Thanks Christopher. I'll try the ldconfig solution. I knew the symbolic links didn't *feel* right so I'm glad I asked! Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.WNT.4.60.0406081310090.3576>