From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Marius Vollmer Newsgroups: gmane.lisp.guile.devel Subject: Re: building guile from CVS Date: Fri, 21 Jan 2005 15:06:42 +0100 Message-ID: References: <873bxarzgk.fsf@zip.com.au> <200501202239.07346.bruno@clisp.org> <87d5vzd6bb.fsf@zip.com.au> <200501211309.39329.bruno@clisp.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106317282 9616 80.91.229.6 (21 Jan 2005 14:21:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 21 Jan 2005 14:21:22 +0000 (UTC) Cc: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Fri Jan 21 15:21:13 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Crzey-0003CA-00 for ; Fri, 21 Jan 2005 15:21:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Crzr0-00079I-QQ for guile-devel@m.gmane.org; Fri, 21 Jan 2005 09:33:38 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CrznC-00064w-NY for guile-devel@gnu.org; Fri, 21 Jan 2005 09:29:42 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Crzmz-0005wS-8T for guile-devel@gnu.org; Fri, 21 Jan 2005 09:29:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Crzmv-0005pG-Q0 for guile-devel@gnu.org; Fri, 21 Jan 2005 09:29:25 -0500 Original-Received: from [129.217.163.1] (helo=mail.dt.e-technik.uni-dortmund.de) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CrzR0-0005UB-GZ for guile-devel@gnu.org; Fri, 21 Jan 2005 09:06:47 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id D942B44234; Fri, 21 Jan 2005 15:06:44 +0100 (CET) Original-Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11661-06-3; Fri, 21 Jan 2005 15:06:44 +0100 (CET) Original-Received: from troy.dt.e-technik.uni-dortmund.de (troy.dt.e-technik.uni-dortmund.de [129.217.163.17]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 4C27D44232; Fri, 21 Jan 2005 15:06:43 +0100 (CET) Original-Received: by troy.dt.e-technik.uni-dortmund.de (Postfix, from userid 520) id 6C7DAB94E; Fri, 21 Jan 2005 15:06:42 +0100 (CET) Original-To: Bruno Haible In-Reply-To: <200501211309.39329.bruno@clisp.org> (Bruno Haible's message of "Fri, 21 Jan 2005 13:09:39 +0100") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de 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:4711 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:4711 Bruno Haible writes: > Configuring guile-core from CVS so that it builds requires a wizard. > Although I can claim to be an old autoconf and automake user, I needed > two hours and the help from Kevin Ryde to get it running. I can feel your pain. :-] Yes, getting Guile to compile from a fresh CVS checkout is not as easy as it can be. But I wouldn't put all the blame on Guile. Guile doesn't do anything out of the ordinary, as far as I am aware (now that we have dropped our own version libltdl), but the autotools still have trouble with it. For example, when no installed libltdl is found, Guile builds its own in the way that libtool prescribes it, but then libtool can't find the freshly build libltdl when we run the freshly build guile executable during the build.[1] There _is_ a big bug in Guile tho (courtesy myself): when checking out guile-core, there is no documentation on how to proceed. These docs are in the file HACKING, but that file is hidden deeply in the guile/workbook module. Not good. I have added a README.CVS file to CVS. Also HACKING didn't talk about the guile-scripts and workbook modules that you need as well in order to build guile-core. I fixed that as well. If that was the source of your frustration, please accept my sincere apologies. > Therefore I'd suggest that you add some instructions to guile-core/autogen.sh > so that it does become so extremely frustrating to attempt to build guile. Why do you want to add instructions to autogen.sh that contradict what autogen.sh is doing itself? Shouldn't we fix autogen.sh, preferably? > # 2) Use these commands to update guile-core: > # $LIBTOOL_PREFIX/bin/libtoolize --force --copy --ltdl > # cp $LIBTOOL_PREFIX/share/aclocal/libtool.m4 guile-config/libtool.m4 I don't want to make Guile more complicated by catering to what could be called 'broken' installations of libtool, etc. If libtoolize is not in the path and libtool.m4 is not found by aclocal, then the installation of libtool is 'broken'. You might bitch that it is too complicated to install libtool correctly, and you are probably right, but hey, I at least don't care. ;-) > # aclocal -I guile-config There are no files in guile-config that are needed by aclocal (except those that you have copied there in step 2.) > # autoconf > # autoheader && touch config.h.in > # automake -a Isn't autoreconf supposed to do this? If it doesn't, it's a bug in autoreconf, right? So, when there are bugs in how we use the autotools, we should of course fix them. If there are simple workarounds for bugs in the latest released versions of the autotools, we should use them as well. But adding instructions to autogen.sh to do manually what autogen.sh is supposed to do automatically is not going to help much, I'm afraid. [1] Hmm, maybe this has something to do with cross-compilation magic that we don't do properly... _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel