From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Greg Troxel Newsgroups: gmane.lisp.guile.devel Subject: Re: The load path Date: 11 Nov 2004 08:23:40 -0500 Message-ID: References: <1097949129.4178.31.camel@localhost> <418C126D.5010802@ossau.uklinux.net> <87u0s3r30n.fsf@trouble.defaultvalue.org> <418D0EAE.40703@ossau.uklinux.net> <1100112232.3368.19.camel@localhost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1100179452 18292 80.91.229.6 (11 Nov 2004 13:24:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 11 Nov 2004 13:24:12 +0000 (UTC) Cc: guile-devel Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Nov 11 14:23:58 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CSEvd-0006XZ-00 for ; Thu, 11 Nov 2004 14:23:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CSF48-000840-U6 for guile-devel@m.gmane.org; Thu, 11 Nov 2004 08:32:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CSF42-00083R-T2 for guile-devel@gnu.org; Thu, 11 Nov 2004 08:32:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CSF40-00082T-QD for guile-devel@gnu.org; Thu, 11 Nov 2004 08:32:37 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CSF40-00082M-LT for guile-devel@gnu.org; Thu, 11 Nov 2004 08:32:36 -0500 Original-Received: from [192.1.100.210] (helo=fnord.ir.bbn.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CSEvN-0003gs-GK for guile-devel@gnu.org; Thu, 11 Nov 2004 08:23:41 -0500 Original-Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 3F5F12394; Thu, 11 Nov 2004 08:23:40 -0500 (EST) Original-To: Andy Wingo In-Reply-To: <1100112232.3368.19.camel@localhost> Original-Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:4372 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:4372 I agree that there is a problem, but I'm not comfortable with hardcoding /usr/local. On NetBSD 2.0, /usr/local/include is _not_ in the default search path for the compiler. One includes -I/-L if one wants that. And, adding /usr/local to guile's search path (as opposed to the prefix with which guile is built, which is already there) doesn't really solve the problem - it just means that guile built with some prefix and some module built with /usr/local will work, not any other combinations. Often people use prefixes to keep things separate. With C libraries, techniques like pkgconfig find linking information, but that's not available. Even still, one has to muck with PKGCONFIGPATH. I think what's needed is first agreement about whether modules installed in prefixes different from guile's prefix should be visible to guile programs that don't set %load-path, and then how to do that in the general case of two different prefixes. One way that seems pretty simple is to have a directory in guile's prefix that has files containing extra directories for %load-path, and a guile utility that takes a prefix and ensures that a file for it is in this directory. Then, modules can simply call guile-prefix-ensure $(prefix) as part of the install process. Alternatively, a similar per-user directory could be used, so that one could do 'guile-prefix-ensure --system' for the global one. I've also symlinked module dirs from another prefix into guile's. This isn't super clean, but it was easy. Binary libraries for modules are another story; IMHO modules should construct absolute paths for their own libraries from the configured prefix, and not rely on search paths. -- Greg Troxel _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel