From owner-freebsd-questions@FreeBSD.ORG Tue Nov 20 22:58:10 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7441616A474 for ; Tue, 20 Nov 2007 22:58:10 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 6922B13C50E for ; Tue, 20 Nov 2007 22:58:10 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (unknown [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 87157654FB for ; Tue, 20 Nov 2007 16:58:09 -0600 (CST) Date: Tue, 20 Nov 2007 16:58:08 -0600 From: Paul Schmehl To: User Questions Message-ID: In-Reply-To: <539c60b90711201434s361ec72co898fad601f35535a@mail.gmail.com> References: <539c60b90711201434s361ec72co898fad601f35535a@mail.gmail.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: arbitrary build can't find libs - right way to do this? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2007 22:58:10 -0000 --On November 20, 2007 3:34:29 PM -0700 Steve Franks wrote: > I'm trying to compile a non-port application for the first time ever. > The associated library built and installed just fine - I can see them > right in /usr/local/lib and usr/local/include/libnamefoo.h However, > when I run ./configure for the application, it clearly can't find the > libs. So my question is, should I be changing my path, is there a > standard variable I need to export, or what? Obviously for ports this > just works, so I've never had to do it. I'm sure there's a standard > way, so I thought I'd get in the habit of doing that right from the > start... > The first thing you should do is read the install docs - usually README and INSTALL. Then run this command in the directory where you untar'd the source files: # ./configure --help This will tell you all the available options for configure, most likely ones like --includedir and --libdir and --bindir and others that may be helpful. As a lost resort you can edit the Makefile to add pointers to the libraries, but that usually is not necessary. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/