From owner-freebsd-questions Sun Oct 31 18:58:47 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 58F6914FFD for ; Sun, 31 Oct 1999 18:58:43 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id TAA13884; Sun, 31 Oct 1999 19:21:56 -0800 (PST) Date: Sun, 31 Oct 1999 19:21:56 -0800 (PST) From: Alfred Perlstein To: Marc Wandschneider Cc: "'Jonathan Chen'" , freebsd-questions@FreeBSD.ORG Subject: RE: (use the ports luke!) RE: your mail In-Reply-To: <13D5F9EDFD72D211BC3100105A1C2233054933@akira.lanfear.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Marc Wandschneider wrote: > > > > -----Original Message----- > > From: Alfred Perlstein [mailto:bright@wintelcom.net] > > Subject: (use the ports luke!) RE: your mail > > > > > > Why? Why do you insist on compiling it yourself and then ask > > questions > > on how to build it when: > > Because, eventually, i'm going to put a library in > /usr/local/lib that's going to cause me to run into this problem again. > The question asked as a general one: where do i tell the system about > libs and headers in /usr/local/XXX. > > i can't believe that this is that obscure that only build > masters would know about such things ... export LD_LIBRARY_PATH=/path1:/path2 and for C includes: export C_INCLUDE_PATH=/path1:/path2 btw, if the port can do it, so can you, just watch/trace what the port does to fix the problem. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message