From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark H Weaver Newsgroups: gmane.lisp.guile.user Subject: Re: guile-2.0 on mingw: the sequel Date: Mon, 26 Aug 2013 02:26:40 -0400 Message-ID: <87ob8l6k7z.fsf@tines.lan> References: <20130825232417.TCPTK.135132.root@cdptpa-web34-z02> <837gf9gogq.fsf@gnu.org> <87sixx6lmk.fsf@tines.lan> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1377498437 10139 80.91.229.3 (26 Aug 2013 06:27:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 26 Aug 2013 06:27:17 +0000 (UTC) Cc: guile-user@gnu.org To: Eli Zaretskii Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Aug 26 08:27:19 2013 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VDqGl-0007I5-33 for guile-user@m.gmane.org; Mon, 26 Aug 2013 08:27:19 +0200 Original-Received: from localhost ([::1]:49261 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VDqGk-0007sg-MO for guile-user@m.gmane.org; Mon, 26 Aug 2013 02:27:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VDqGV-0007oK-Hq for guile-user@gnu.org; Mon, 26 Aug 2013 02:27:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VDqGM-0007na-93 for guile-user@gnu.org; Mon, 26 Aug 2013 02:27:03 -0400 Original-Received: from world.peace.net ([96.39.62.75]:40667) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VDqGM-0007nO-4g; Mon, 26 Aug 2013 02:26:54 -0400 Original-Received: from 209-6-91-212.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.91.212] helo=tines.lan) by world.peace.net with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1VDqGF-00012Y-Gj; Mon, 26 Aug 2013 02:26:47 -0400 In-Reply-To: <87sixx6lmk.fsf@tines.lan> (Mark H. Weaver's message of "Mon, 26 Aug 2013 01:56:19 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 96.39.62.75 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:10716 Archived-At: I wrote: > I can think of one notable case where the program would know where > libguile is located: when the program bundles its own copy of Guile, and > therefore assumes that libguile and the program are always moved > together as an atomic unit. > > This practice is frowned upon on most POSIX systems (and rightfully so), > but I guess it's fairly common on Windows and MacOS X systems. For what it's worth, I _do_ think that we should support this use case, and therefore I agree that it would probably be useful to have the API you suggested, where the program can tell libguile where libguile is located. However, the only case where this API could reasonably be used is when libguile is bundled with the program in question, because that's the only case where the program would reliably know the location of the libguile that the dynamic linker found. Regards, Mark