From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: updated $workbook/modules/modules-and-shared-libs.text Date: Tue, 21 May 2002 15:16:32 -0700 Sender: guile-user-admin@gnu.org Message-ID: References: <20020521173935.5f721206.dsmith@altustech.com> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1022019695 26059 127.0.0.1 (21 May 2002 22:21:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 21 May 2002 22:21:35 +0000 (UTC) Cc: guile-user@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17AI0c-0006m9-00 for ; Wed, 22 May 2002 00:21:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17AI0P-0003gN-00; Tue, 21 May 2002 18:21:21 -0400 Original-Received: from ca-crlsbd-u5-c4a-a-172.crlsca.adelphia.net ([24.48.214.172] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17AHzb-0003dh-00 for ; Tue, 21 May 2002 18:20:32 -0400 Original-Received: from ttn by giblet with local (Exim 3.35 #1 (Debian)) id 17AHvk-0001kx-00; Tue, 21 May 2002 15:16:32 -0700 Original-To: dsmith@altustech.com In-Reply-To: <20020521173935.5f721206.dsmith@altustech.com> Errors-To: guile-user-admin@gnu.org X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.user:466 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:466 From: "Dale P. Smith" Date: Tue, 21 May 2002 17:39:35 -0400 [ lot's of stuff about the way modules/shared-libraries have changed ] I just noticed something recently: I can no longer load a .so file from guile 1.6.x using load-extension. I had to make a .la file (by copying one that was already in /usr/local/lib and editing it suitably) for it to work. Is it now necessary to use libtool (or whatever it's called) to make a .so that Guile can load? Am I finally going to have to roll up my sleeves and dig into the auto* tools maze? i could answer in a sneaky way, but let me lay my agenda bare: i want to encourage users to get to know guile inside as well as out so that they can maintain it over the long run. this entails some learning; if we record what we learn (instead of discussing aimlessly on mailing lists w/ no conclusion) that's not so bad. so if by-the-by you learn more about the auto* tools (and share that), i think guile will benefit. as for the particular hatchet job that is load-extension and all that it entails, i partially sympathize w/ the intent of simplifying things. to be useful though, you cannot simplify too much, which is what happened. so to answer your question, it depends on what kind of time scope you're prepared to put into it: if you think in the long-term, you can help design the "build-guile-compiled-module" program, starting at the user interface (specifying command-line args/options), and someone (me or you if you gain write privs and get to know libtool) will make it so. this design is then likely to be available w/ guile-1.6.x (or its successor should 1.6.x be prematurely released). if you think in the medium- or short-term, probably that means you want to work around 1.6.x deficiencies, in which case i cannot help, because to me all infrastructure-related work should be done in the context of long-term thinking. thi _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://mail.gnu.org/mailman/listinfo/guile-user