<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.lisp.clbuild.devel">
    <title>gmane.lisp.clbuild.devel</title>
    <link>http://blog.gmane.org/gmane.lisp.clbuild.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/346"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/344"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/342"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/337"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/336"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/333"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/332"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/331"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/330"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/328"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/327"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/325"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/324"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/323"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/322"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/321"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/319"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/318"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/316"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.clbuild.devel/315"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/346">
    <title>patch for clbuild on ECL 11.1.1</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/346</link>
    <description>&lt;pre&gt;dear clbuild maintainers,

I found a couple of small problems when using clbuild with ECL 11.1.1
(the latest release of ECL).

Please find the patch attached.

The patch solves the following problems:

In clbuild2/internal/ the name of the script for ECL is imcl-ecl.sh
(please note there's a `c' instead of a `p').

After changing the name of the script, clbuild complains with

   Cannot find the external symbol QUIT in #&amp;lt;"COMMON-LISP-USER" package&amp;gt;

As of ECL 11.1.1, QUIT is defined in EXT.

That's it.

Thanks for clbuild!

--
Simón Ortiz B., M.Sc., Ing. en Computación
Linux Registered User #388735
&lt;/pre&gt;</description>
    <dc:creator>Simon Ortiz</dc:creator>
    <dc:date>2011-07-02T06:21:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/344">
    <title>Pull request for some minor patches to command-lineusage messages</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/344</link>
    <description>&lt;pre&gt;Hi,

The patches are from 37425c3 to cf17787 [1].

They simply bail out earlier (instead of loading a lisp image) when
required parameters are missing and provide usage messages.  One is
just a fix to an existing message.

[1] git://gitorious.org/~dwhite/clbuild2/clbuild2-daniel.git

Regards,

&lt;/pre&gt;</description>
    <dc:creator>Daniel White</dc:creator>
    <dc:date>2011-05-16T18:23:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/342">
    <title>Getting clbuild via git</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/342</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Greg Bennett</dc:creator>
    <dc:date>2011-01-27T19:39:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/337">
    <title>clbuild2 and CCL</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/337</link>
    <description>&lt;pre&gt;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 &amp;lt;http://www.sbcl.org/&amp;gt;.

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?

&lt;/pre&gt;</description>
    <dc:creator>Greg Pfeil</dc:creator>
    <dc:date>2011-01-03T23:35:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/336">
    <title>ASDF source registry woes</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/336</link>
    <description>&lt;pre&gt;Hello,

I recently noticed that my clbuild2-built lisp image was not picking
up new systems from ~/src/lisp/*/ despite having the proper ASDF
source registry :tree configuration in place. I fixed this by calling
asdf:clear-source-registry at the end of asdf-setup.lisp[1].

However, I fear that I might be missing some subtlety in the previous
source registry clearing code. My system seems to able to find the
SBCL contribs; is that good enough a test?

Cheers,


[1] &amp;lt;http://gitorious.org/~luismbo/clbuild2/clbuild2-luis/commit/73ad98a67a4d269fe3028a035f4f169952b11d17&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>Luís Oliveira</dc:creator>
    <dc:date>2010-12-06T20:58:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/333">
    <title>Postmodern repo moved (again)</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/333</link>
    <description>&lt;pre&gt;Long story short, Google delisted my domain for no reason at all,
didn't give me a way to fix that, so I moved to a new domain. I set up
a redirect, but unfortunately git doesn't seem to handle those very
well. Postmodern is now:

  git clone http://marijn.haverbeke.nl/git/postmodern

(Also, the dependencies listed for postmodern are off -- it doesn't
use lift, and it no longer uses ieee-floats and trivial-utf-8.)

Best,
Marijn

&lt;/pre&gt;</description>
    <dc:creator>Marijn Haverbeke</dc:creator>
    <dc:date>2010-11-28T19:59:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/332">
    <title>clbuild 2.0 in git with Quicklisp integration</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/332</link>
    <description>&lt;pre&gt;Hello list,

it has been silent around clbuild for some time now, both on the list
and in the repository.

Part of that may be because clbuild simply works for its users :-), but
I imagine other reasons to have been:

  - lack of ASDF2 support, meaning that the inclusion of ASDF2 support
    in SBCL has made it hard to work with clbuild meaningfully

  - the appearance of Quicklisp, arguably one of the most important
    projects out there right now for the free lisp software community

  - last not least the areas in which clbuild has never been
    particularly strong, and which Quicklisp covers better, i.e. mainly
    the quick downloading of large numbers of projects, as is needed for
    the initial download or update of projects with many dependencies.

I am happy to announce the release of a new version of clbuild designed
to address these shortcomings.

Some of you will already heard about this new version on IRC.  It was
called qlbuild while it was only an idea, and retained the name qlbuild
while I started hacking on that idea.

I have now decided to ditch the qlbuild name, and rename it back to
clbuild, version 2.0.

clbuild 2.0 features the following:

  - support for ASDF2 (and only ASDF2)

  - integration with QuickLisp

  - concentration on clbuild's core competencies (i.e., easy Lisp and
    slime startup, download of projects from version control, SBCL
    building) while dropping features that other projects do better
    (dependency tracking, tarball downloading).  The latter are all done
    through Quicklisp now.

  - some overall refactoring.  The large shell script was split into
    multiple files.

The new project is maintained in git, not darcs, and can be found at:

  http://gitorious.org/clbuild2
  git clone git://gitorious.org/clbuild2/clbuild2.git

(Note the version number in the URL -- I would like to drop that number
from the gitorious project name if possible, but there is an unrelated
git fork of clbuild on gitorious, which is named just clbuild, and is
based more directly on the old darcs version, I believe.)

Please note that the refactoring effort has meant that some features got
dropped, simply because I started from scratch with a minimal script,
and added features back only bit by bit.  If any feature important to
you is missing, let's discuss its inclusion.  Some changes are
intentional though.  Please see the file DESIGN-NOTES in the repository
for a brief overview.

Finally, please note that I haven't updated the clbuild web page on
common-lisp.net yet.  Unless there is a huge outcry over my changes, I
am planning on rewriting that page to discuss clbuild2 instead of
classic clbuild though.


d.

&lt;/pre&gt;</description>
    <dc:creator>David Lichteblau</dc:creator>
    <dc:date>2010-11-13T13:22:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/331">
    <title>git.b9.com</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/331</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Bryan Green</dc:creator>
    <dc:date>2010-10-01T22:21:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/330">
    <title>git.b9.com</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/330</link>
    <description>&lt;pre&gt;
Anybody else experience problems with git.b9.com right now?

: pangea clbuild; ./clbuild install cl-base64
MISMATCH: cl-base64 was installed from /home/petter/projects/lisp-libraries/clbuild/source/cl-base64
git://git.b9.com/cl-base64.git, current is git://git.b9.com/cl-base64.git
UPDATE git pull cl-base64
/home/petter/projects/lisp-libraries/clbuild/source/cl-base64
git.b9.com[0: 216.184.11.2]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)

error: update was interrupted.
Use "clbuild update --resume" to retry.  (See also "clbuild skip PROJECT").


//Petter



&lt;/pre&gt;</description>
    <dc:creator>Petter Gustad</dc:creator>
    <dc:date>2010-09-28T19:27:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/328">
    <title>compile-implementation sbcl</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/328</link>
    <description>&lt;pre&gt;

It appears to be a problem with how clbuild organize the fasl's and
where sbcl locates the constants.lisp-temp file:


darcs get http://common-lisp.net/project/clbuild/clbuild
cd clbuild
chmod a+x clbuild
./clbuild update sbcl
./clbuild compile-implementation sbcl
./clbuild lisp --eval "(progn (print (lisp-implementation-version)) (asdf:oos 'asdf:load-op :sb-posix))"

"1.0.42.52" 

debugger invoked on a SB-INT:SIMPLE-FILE-ERROR in thread #&amp;lt;THREAD
                                                           "initial thread" RUNNING
                                                           {1002AAFEA1}&amp;gt;:
  failed to find the TRUENAME of /home/petter/.fasls/sbcl-1.0.42.52-linux-x86-64/tmp/clbuild-test/clbuild/target/lib/sbcl/sb-posix/constants.lisp-temp:
    No such file or directory


Have this issue been resolved in some development branch or elsewhere?
How do you avoid this problem if you're using clbuild/sbcl/sb-posix?

Thanks

//Petter



&lt;/pre&gt;</description>
    <dc:creator>Petter Gustad</dc:creator>
    <dc:date>2010-09-23T12:54:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/327">
    <title>Add GBBopen</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/327</link>
    <description>&lt;pre&gt;The following projects line adds GBBopen to clbuild:

gbbopen get_svn http://gbbopen.org/svn/GBBopen/trunk/ #blackboard-system framework, tools, &amp;amp; utilities

Thanks!
&lt;/pre&gt;</description>
    <dc:creator>Dan Corkill</dc:creator>
    <dc:date>2010-08-21T14:48:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/325">
    <title>dwim projects dependencies</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/325</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Gustavo</dc:creator>
    <dc:date>2010-08-18T13:00:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/324">
    <title>A swank server-only task?</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/324</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Abhishek Reddy</dc:creator>
    <dc:date>2010-08-10T01:31:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/323">
    <title>swank preload doc error</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/323</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Abhishek Reddy</dc:creator>
    <dc:date>2010-08-10T01:40:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/322">
    <title>added support for CLON</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/322</link>
    <description>&lt;pre&gt;I've added CLON (periodic scheduled timer support) to the wnpp-projects 
file, as well as its one dependency, trivial-timers. This project is 
based on the sbcl timers implementation, so I don't think it's terribly 
portable, but it works great on sbcl and is quite useful. I dunno what 
the policy about portability between implementations is for clbuild 
projects... at any rate, if it's deemed useful, please darcs pull from :

http://coruscant.deepsky.com/~fade/clbuild

thanks!

Brian

&lt;/pre&gt;</description>
    <dc:creator>Brian O'Reilly</dc:creator>
    <dc:date>2010-07-21T17:01:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/321">
    <title>Programming for clbuild McClim</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/321</link>
    <description>&lt;pre&gt;Hello!

Hope it is ok that I am sending this question to this list, I found no
other way to get in contact with the clbuild project and couldn't
search the mailing lists. I've just had clbuild install SBCL and
McClim for me (I can run demodemo), but can't use McClim myself. What
I've tried doing is ./clbuild lisp and then (require :climxm), but the
interpreter gives me an error saying it doesn't know how to require
climxm.

Is there a convenient way to get started with CLIM programming using
clbuild, or will I have to look into setting up my own system? If so,
does anybody know of a convenient way to get started quickly?
Deployment will be on an AllegroCL with Allegro's CLIM implementation,
which I'll soon have X11-forwarding access to, but I want to be able
to run it locally as well (telecommuting, and I don't trust my
employer's uptimes).

Regards,
Oliver Uvman

&lt;/pre&gt;</description>
    <dc:creator>Oliver</dc:creator>
    <dc:date>2010-07-09T16:09:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/319">
    <title>get_github, repo updates</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/319</link>
    <description>&lt;pre&gt;http://3bb.cc/tmp/darcs/clbuild/  adds a helper to download repos from
github (optionally from writable repo for specified user if
GITHUB_USER is set), and updates cl-opengl, swf2, and trivial-shell to
use their new github repos.

-b

&lt;/pre&gt;</description>
    <dc:creator>Bart Botta</dc:creator>
    <dc:date>2010-06-02T23:16:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/318">
    <title>wrong syntax for lispbuilder in wnpp-projects</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/318</link>
    <description>&lt;pre&gt;hello.

the get_svn commands are missing before the svn-adresses of the
lispbuilder-projects in wnpp-projects. it doesnt work without them. (i
could provide a patch but presumably its easier to just add them
manually instead)

regards,

christoph

&lt;/pre&gt;</description>
    <dc:creator>Christoph Senjak</dc:creator>
    <dc:date>2010-05-18T21:13:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/316">
    <title>iolib and lisp-on-lines repo updates</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/316</link>
    <description>&lt;pre&gt;I have updated the location of the iolib repo to reflect the repository 
listed on the iolib project web page as canonical, and to get around a 
problem in the current http:// location at common-lisp.net. I have also 
updated the location of the lisp-on-lines project repository to reflect 
the request drew crampsie made to this list on 23/01/10. Each change is 
a single patch, and both have been tested in clean checkouts this time. 
Please pull from: http://coruscant.deepsky.com/~fade/clbuild/

..Brian

&lt;/pre&gt;</description>
    <dc:creator>Brian O'Reilly</dc:creator>
    <dc:date>2010-05-15T21:59:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/315">
    <title>patch: Trivial-Shell broken in clbuild</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/315</link>
    <description>&lt;pre&gt;Seems like trivial-shell has moved to git. I changed the wnpp-projects
file. Have the REPO in

http://uxul.vserverkompetenz.de/software/clbuild

Regards, Christoph

&lt;/pre&gt;</description>
    <dc:creator>Christoph Senjak</dc:creator>
    <dc:date>2010-05-08T23:02:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.clbuild.devel/311">
    <title>Broken repository for lift</title>
    <link>http://comments.gmane.org/gmane.lisp.clbuild.devel/311</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Juan Jose Garcia-Ripoll</dc:creator>
    <dc:date>2010-04-26T08:52:39</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.lisp.clbuild.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.lisp.clbuild.devel</link>
  </textinput>
</rdf:RDF>

