Headache is just a hack away.
in [Lisp]
|
Prev: Toronto Lisp Users Group meeting, Tuesday April 6
Next: Apply your understanding of Accounts and Statistics
From: Norbert_Paul on 6 Apr 2010 12:50 Tamas K Papp wrote: > I disagree, CLC was more of a source of a headache for me than an > useful layer. My Lisp experience on Debian has been the smoothest > with clbuild (for SLIME, libraries) and an SBCL compiled from source. > I only use the Debian-packaged SBCL to compile the latter. Yeah! Now I have Debian squeeze + slime + sbcl running together! (Note that Debian's slime + Debian's sbcl crashed on my box). I also did $clbuild projects|grep cmu and it seems as if clbuild didn't know cmucl. Is that true? But then I can't test the latest CMU release which initially was the point of that recent install party. Besides, what would be a convenient location for the clbuild tree? Now, I have it at $HOME/clbuild with root rights which looks strange. Norbert
From: Tamas K Papp on 7 Apr 2010 08:13 On Tue, 06 Apr 2010 18:50:18 +0200, Norbert_Paul wrote: > Tamas K Papp wrote: >> I disagree, CLC was more of a source of a headache for me than an >> useful layer. My Lisp experience on Debian has been the smoothest with >> clbuild (for SLIME, libraries) and an SBCL compiled from source. I only >> use the Debian-packaged SBCL to compile the latter. > Yeah! > Now I have Debian squeeze + slime + sbcl running together! (Note that > Debian's slime + Debian's sbcl crashed on my box). > > I also did > $clbuild projects|grep cmu > and it seems as if clbuild didn't know cmucl. Is that true? But then I > can't test the latest CMU release which initially was the point of that > recent install party. AFAIK CMUCL is not supported, but you can always install it separately. > Besides, what would be a convenient location for the clbuild tree? Now, > I have it at $HOME/clbuild with root rights which looks strange. Anywhere. I have it in software/clbuild. I don't see why it has to be root: libraries certainly don't need to be root, SBCL compiles file for any user, I just su for make install. But even that is not needed if you set up the paths for SBCL. So just do everything as a regular user. Tamas
From: Norbert_Paul on 7 Apr 2010 10:55 Tamas K Papp wrote: > On Tue, 06 Apr 2010 18:50:18 +0200, Norbert_Paul wrote: > AFAIK CMUCL is not supported, but you can always install it > separately. I did that. I was just wondering- > Anywhere. I have it in software/clbuild. I don't see why it has to > be root: libraries certainly don't need to be root, SBCL compiles file > for any user, I just su for make install. But even that is not needed > if you set up the paths for SBCL. So just do everything as a regular > user. OK. Besides, then do you have 'software' at ${HOME}? I thought, I should be root, as I am used to installing software as root. Sometimes, however, when I'm lazy (err ... "often"?), I install(ed?) my Java libraries at ${HOME}. Norbert
From: Tamas K Papp on 7 Apr 2010 11:09
On Wed, 07 Apr 2010 16:55:54 +0200, Norbert_Paul wrote: > Tamas K Papp wrote: >> On Tue, 06 Apr 2010 18:50:18 +0200, Norbert_Paul wrote: AFAIK CMUCL is >> not supported, but you can always install it separately. > I did that. I was just wondering- > >> Anywhere. I have it in software/clbuild. I don't see why it has to be >> root: libraries certainly don't need to be root, SBCL compiles file for >> any user, I just su for make install. But even that is not needed if >> you set up the paths for SBCL. So just do everything as a regular >> user. > OK. > Besides, then do you have 'software' at ${HOME}? I thought, I should be > root, as I am used to installing software as root. Sometimes, however, > when I'm lazy (err ... "often"?), I install(ed?) my Java libraries at > ${HOME}. All of the Common Lisp software I use, including libraries and SBCL, is inside my home directory, managed as a regular user. The only thing I use root for is installing SBCL ("sh install.sh"). Tamas |