Date: Sun, 31 Oct 1999 19:21:56 -0800 (PST) From: Alfred Perlstein <bright@wintelcom.net> To: Marc Wandschneider <MarcW@Lanfear.com> Cc: "'Jonathan Chen'" <jonc@logisticsoftware.co.nz>, freebsd-questions@FreeBSD.ORG Subject: RE: (use the ports luke!) RE: your mail Message-ID: <Pine.BSF.4.05.9910311920130.12797-100000@fw.wintelcom.net> In-Reply-To: <13D5F9EDFD72D211BC3100105A1C2233054933@akira.lanfear.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9910311920130.12797-100000>