From owner-freebsd-ports@FreeBSD.ORG Tue Jun 8 20:13:16 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 512C516A4D0 for ; Tue, 8 Jun 2004 20:13:16 +0000 (GMT) Received: from mail.blarg.net (floyd.blarg.net [206.124.128.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 085AD43D39 for ; Tue, 8 Jun 2004 20:13:16 +0000 (GMT) (envelope-from andrewc@blarg.net) Received: from tkitgprxya11.redmond.corp.microsoft.com (tide138.microsoft.com [207.46.238.138]) by mail.blarg.net (Postfix) with ESMTP id 7743838065; Tue, 8 Jun 2004 13:13:14 -0700 (PDT) Date: Tue, 8 Jun 2004 13:13:12 -0700 (Pacific Daylight Time) From: Andrew Carter To: Christopher Nehren In-Reply-To: <20040608181840.GA79388@prophecy.dyndns.org> Message-ID: References: <20040608181840.GA79388@prophecy.dyndns.org> X-X-Sender: andrewc@mail.blarg.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: "freebsd-ports@freebsd.org" Subject: Re: Subversion 1.0.4 install problem X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2004 20:13:16 -0000 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