I tried this -- no go, including using gsl-devel.  Also installed gsl from source and gsll still won't install.  I'm going to try with ccl now.

On Mon, Aug 16, 2010 at 10:47 AM, Glen Henshaw <glen.henshaw@gmail.com> wrote:
It would be

> sudo port selfupdate
> sudo port upgrade gsl

Assuming you are using macports. I don't know what the fink equivalent would be.

Glen

Glen Henshaw, PhD • Roboticist • U.S. Naval Research Laboratory
office: 202-767-1196 • google voice/mobile: 443-295-3050
glen.henshaw@nrl.navy.mil

On Aug 15, 2010, at 3:44 PM, James Wright <james@chumsley.org> wrote:

> Hi David,
>
> The command I gave (darcs send) was the command that I used to
> generate the patch, not to apply it.  (i.e., I generated a patch that
> Liam could send to the clbuild project to get gsll included in the
> stock clbuild install).
>
> If you have already added the lines that Liam described, then my patch
> is probably irrelevant to you.  If you haven't added the lines and
> want to use my patch to do so, then you could try
>
> darcs apply gsll-clbuild.patch
>
> followed by
>
> ./clbuild install gsll
>
> From the errors you've listed, I can't really see what's going wrong,
> but it doesn't look to me to be clbuild related.  Have you got the
> development version of libgsl installed?  I used
>
> sudo apt-get install libgsl0-dev
>
> to install the headers and so forth for libgsl on my Ubuntu box; I
> don't know what the OS X equivalent would be.
>
> hth,
>      James
>
> On Sun, Aug 15, 2010 at 8:18 AM, David Dreisigmeyer
> <david.dreisigmeyer@gmail.com> wrote:
>> Hi James,
>> Am I doing this correctly(?):
>> new-host:clbuild daviddreisigmeyer$ ls
>> .                          .core-is-stale
>> clbuild-bash-completion.sh dependencies               implementations
>>      systems
>> ..                         _darcs                     clbuild.conf.default
>>     doc                        projects                   target
>> .DS_Store                  clbuild                    clbuild.lisp
>>     gsll-clbuild.patch         source                     wnpp-projects
>> new-host:clbuild daviddreisigmeyer$ darcs send -o gsll-clbuild.patch
>> Creating patch to "http://common-lisp.net/project/clbuild/clbuild"...
>> No recorded local changes to send!
>> new-host:clbuild daviddreisigmeyer$
>>
>> Here's part of the error from emacs using (asdf:operate 'asdf:load-op
>> :gsll):
>>   7: (CFFI-GROVEL::GENERATE-C-FILE
>> #P"/Users/daviddreisigmeyer/lisp/clbuild/clbuild/source/gsll/init/libgsl-unix.lisp"
>> #P"/Users/daviddreisigmeyer/lisp/clbuild/clbuild/source/gsll/init/libgsl-unix.fasl")
>>       Locals:
>>         SB-DEBUG::ARG-0 =
>> #P"/Users/daviddreisigmeyer/lisp/clbuild/clbuild/source/gsll/init/libgsl-un..
>>         SB-DEBUG::ARG-1 =
>> #P"/Users/daviddreisigmeyer/lisp/clbuild/clbuild/source/gsll/init/libgsl-un..
>>
>> The file libgsl-unix.c that's generated (?) is empty also -- don't know if
>> that helps.
>> On Fri, Aug 13, 2010 at 4:11 PM, James Wright <james@chumsley.org> wrote:
>>>
>>> Hi Liam,
>>>
>>>> Yeah, well the clbuild instructions *used* to be on the web page, but
>>>> I took them out because
>>>> of all the changes, and I just figured I'd get the clbuild people to
>>>> add appropriate lines.
>>>> That didn't happen in turn because I can't figure out how to make a
>>>> darcs diff which is
>>>> how they take all patches.
>>>
>>> I've generated a darcs diff from the stock clbuild.  It's attached in
>>> case that is helpful.  The command that I used was "darcs send -o
>>> gsll-clbuild.patch".
>>>
>>>      James
>>>
>>> _______________________________________________
>>> Gsll-devel mailing list
>>> Gsll-devel@common-lisp.net
>>> http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel
>>>
>>
>>
>
> _______________________________________________
> Gsll-devel mailing list
> Gsll-devel@common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel