From owner-freebsd-questions Tue Oct 10 17:31: 7 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 9FFAB37B502 for ; Tue, 10 Oct 2000 17:31:05 -0700 (PDT) Received: (qmail 61781 invoked by uid 100); 11 Oct 2000 00:30:57 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14819.46272.982612.387928@guru.mired.org> Date: Tue, 10 Oct 2000 19:30:56 -0500 (CDT) To: Michael Lucas Cc: questions@freebsd.org Subject: Re: library-port matching tool? In-Reply-To: <127489075@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas writes: > More than once, I've had this problem where a software package won't > run because a library is missing. If you're installing FreeBSD packages, they should notice the dependency and install the package for you. If they're not doing that, notify the maintainer of the port from which the package is built. > Do we have a generalized method of looking up a library to find out > what port it's in? Yes, but it sucks: find /usr/ports -name PLIST | xargs grep I had expected "make search key=" to work, but it didn't :-(.