From greg at technomadic.org Mon Jan 3 23:35:35 2011 From: greg at technomadic.org (Greg Pfeil) Date: Mon, 3 Jan 2011 18:35:35 -0500 Subject: [clbuild-devel] clbuild2 and CCL Message-ID: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> I'm trying to use clbuild2 with CCL and have had a couple issues. One is that there seems to be a bug with "--implementation" (diff attached). The other is that (after I've applied the aforementioned patch) when I do: clbuild --implementation ccl slime it still tries to use SBCL: $ clbuild --implementation ccl slime clbuild: no valid core file /home/lisp/greg/clbuild2/sbcl-base.core, dumping now... This is SBCL 1.0.31.0.debian, an implementation of ANSI Common Lisp. More information about SBCL is available at . SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * Any suggestions? -------------- next part -------------- A non-text attachment was scrubbed... Name: implementation.patch Type: application/octet-stream Size: 291 bytes Desc: not available URL: From david at lichteblau.com Tue Jan 4 21:05:54 2011 From: david at lichteblau.com (David Lichteblau) Date: Tue, 4 Jan 2011 22:05:54 +0100 Subject: [clbuild-devel] clbuild2 and CCL In-Reply-To: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> References: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> Message-ID: <20110104210554.GA1586@radon> Quoting Greg Pfeil (greg at technomadic.org): > I'm trying to use clbuild2 with CCL and have had a couple issues. One is that there seems to be a bug with "--implementation" (diff attached). > > The other is that (after I've applied the aforementioned patch) when I do: > > clbuild --implementation ccl slime > > it still tries to use SBCL: [...] Two issues: - Option processing happened too late, after loading the sources. - To keep things simple, clbuild intentionally does not default LISP_BINARY based on LISP_IMPLEMENTATION_TYPE anymore, which means that clbuild doesn't know about all of CCL's weird binary names like lx86cl64. I have pushed support for --implementation and two new options, --type and --binary. Please test! Explanation: In clbuild2, the user-specific configuration file clbuild.conf is tasked with setting both LISP_IMPLEMENTATION_TYPE and LISP_BINARY (as well as other variables needed, like SBCL_HOME or CCL_DEFAULT_DIRECTORY; a default for the latter is computed if missing though). Hence the new options --type (corresponding to LISP_IMPLEMENTATION_TYPE) and --binary (corresponding to LISP_BINARY). The existing option --implementation /path/to/xylisp is now parsed as --type xylisp --binary /path/to/xylisp. Option processing first sets variables FORCE_LISP_IMPLEMENTATION_TYPE and FORCE_LISP_BINARY. It then runs clbuild.conf, and only afterwards overrides the usual configuration with the values of the FORCE_* variables, if FORCE_* is still set. The goal of that logic is to give clbuild.conf a chance to override or customize the values specified on the command line. So the following works out of the box for me now: clbuild --type ccl --binary ~/usr/ccl-1.6/lx86cl64 lisp And the short version is possible, but depends on user-specific customization in clbuild.conf to teach clbuild that the user intends ccl to be a shortcut for lx86cl64: clbuild --implementation ccl lisp The clbuild.conf snippet for that would look like this: case $FORCE_LISP_IMPLEMENTATION_TYPE in ccl) FORCE_LISP_BINARY=~/usr/ccl-1.6/lx86cl64 ;; esac More examples in clbuild.conf.default. d. From greg at technomadic.org Wed Jan 5 20:26:12 2011 From: greg at technomadic.org (Greg Pfeil) Date: Wed, 5 Jan 2011 15:26:12 -0500 Subject: [clbuild-devel] clbuild2 and CCL In-Reply-To: <20110104210554.GA1586@radon> References: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> <20110104210554.GA1586@radon> Message-ID: <20C6F03F-DCEE-43AB-8F72-646E62F409D3@technomadic.org> On 4 Jan 2011, at 16:05, David Lichteblau wrote: > Two issues: > > - Option processing happened too late, after loading the sources. > > - To keep things simple, clbuild intentionally does not default > LISP_BINARY based on LISP_IMPLEMENTATION_TYPE anymore, which means > that clbuild doesn't know about all of CCL's weird binary names > like lx86cl64. > > I have pushed support for --implementation and two new options, --type > and --binary. Please test! The way I have things set up, CCL is called `ccl` and it's in $PATH, so all of the following work: ? clbuild --type ccl --binary /usr/local/bin/ccl lisp ? clbuild --type ccl --binary ccl lisp ? clbuild --implementation /usr/local/bin/ccl lisp ? clbuild --implementation ccl lisp However, as soon as I change `lisp` to `slime`, I end up in SBCL again. Seems like this is because of (setq inferior-lisp-program "/home/lisp/greg/clbuild2/clbuild lisp") in .start-slime.el. A simple solution might be to export a var with the command-line args used to start clbuild (sans "slime"), and then look that up from the .el file. I understand that using a conf file should avoid this issue, but I figured I should point it out. Thanks for the tool. From david at lichteblau.com Wed Jan 5 20:57:37 2011 From: david at lichteblau.com (David Lichteblau) Date: Wed, 5 Jan 2011 21:57:37 +0100 Subject: [clbuild-devel] clbuild2 and CCL In-Reply-To: <20C6F03F-DCEE-43AB-8F72-646E62F409D3@technomadic.org> References: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> <20110104210554.GA1586@radon> <20C6F03F-DCEE-43AB-8F72-646E62F409D3@technomadic.org> Message-ID: <20110105205737.GA15269@radon> Quoting Greg Pfeil (greg at technomadic.org): > However, as soon as I change `lisp` to `slime`, I end up in SBCL again. Seems like this is because of > > (setq inferior-lisp-program "/home/lisp/greg/clbuild2/clbuild lisp") > > in .start-slime.el. A simple solution might be to export a var with the command-line args used to start clbuild (sans "slime"), and then look that up from the .el file. > > I understand that using a conf file should avoid this issue, but I figured I should point it out. > > Thanks for the tool. Good point. Fix pushed; please test. From greg at technomadic.org Wed Jan 5 21:10:09 2011 From: greg at technomadic.org (Greg Pfeil) Date: Wed, 5 Jan 2011 16:10:09 -0500 Subject: [clbuild-devel] clbuild2 and CCL In-Reply-To: <20110105205737.GA15269@radon> References: <77844957-98AA-46F4-A851-FE6483340165@technomadic.org> <20110104210554.GA1586@radon> <20C6F03F-DCEE-43AB-8F72-646E62F409D3@technomadic.org> <20110105205737.GA15269@radon> Message-ID: On 5 Jan 2011, at 15:57, David Lichteblau wrote: > Quoting Greg Pfeil (greg at technomadic.org): >> However, as soon as I change `lisp` to `slime`, I end up in SBCL again. Seems like this is because of >> >> (setq inferior-lisp-program "/home/lisp/greg/clbuild2/clbuild lisp") >> >> in .start-slime.el. A simple solution might be to export a var with the command-line args used to start clbuild (sans "slime"), and then look that up from the .el file. >> >> I understand that using a conf file should avoid this issue, but I figured I should point it out. >> >> Thanks for the tool. > > Good point. Fix pushed; please test. Yep, that seems to have done it. Gracias. From gwbennett at sentex.ca Thu Jan 27 19:39:39 2011 From: gwbennett at sentex.ca (Greg Bennett) Date: Thu, 27 Jan 2011 14:39:39 -0500 Subject: [clbuild-devel] Getting clbuild via git Message-ID: <4D41C9FB.4080809@sentex.ca> Hello there from Greg Bennett I have encountered a 'fatal:' message in attempting to get clbuild via git. Running Ubuntu 10.4 64-bit, I believe I am following the web page in issuing git clone git:://gitorious.org/clbuild2/clbuild2.git and I receive in return Initialized empty Git repository in /home/gwbennett/LispTopLevel/Systems/clbuild/clbuild2/.git/ fatal: unable to find remote helper for 'git' Perhaps someone can point out my error(s) Cheers /Greg Bennett -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at lichteblau.com Thu Jan 27 20:38:49 2011 From: david at lichteblau.com (David Lichteblau) Date: Thu, 27 Jan 2011 21:38:49 +0100 Subject: [clbuild-devel] Getting clbuild via git In-Reply-To: <4D41C9FB.4080809@sentex.ca> References: <4D41C9FB.4080809@sentex.ca> Message-ID: <20110127203849.GA19031@radon> Hi there, Quoting Greg Bennett (gwbennett at sentex.ca): > Hello there from Greg Bennett > I have encountered a 'fatal:' message in attempting to get clbuild via git. > Running Ubuntu 10.4 64-bit, I believe I am following the web page in issuing > > git clone git:://gitorious.org/clbuild2/clbuild2.git > > and I receive in return > > Initialized empty Git repository in > /home/gwbennett/LispTopLevel/Systems/clbuild/clbuild2/.git/ > fatal: unable to find remote helper for 'git' > > Perhaps someone can point out my error(s) Gladly :-). There's a colon too many in git:://. The right command reads: git clone git://gitorious.org/clbuild2/clbuild2.git > Cheers /Greg Bennett David