run-tests results on OS X mavericks

[Munawar Cheema]

Thanks David,
The patch makes sense I'll try it out. I was going to check what
failed exactly but didn't want to do so till I was sure it wasn't
something I had done.  I'll go ahead with it now.


On Fri, Jul 3, 2015 at 8:40 AM, David Catteeuw <davidcatteeuw at gmail.com> wrote:
> Hi Munawar,
>
> On Thu, Jul 2, 2015 at 11:49 PM, Munawar Cheema <munawar.a.cheema at gmail.com>
> wrote:
>>
>> I installed gsll from quicklisp. I had to manually give values for the
>> libgsl and libgslclas to get the install to work.
>
>
> I've been using the patch below to fix this problem in gsll's initialisation
> code. I think it should use "gsl-config --libs" instead of "gsl-config
> --prefix" to find libgsl.
>
> --- a/gsll-20140211-git/init/init.lisp  2014-04-28 11:48:43.000000000 +0800
> +++ b/gsll-20140211-git/init/init.lisp  2014-04-28 12:15:59.000000000 +0800
> <at>  <at>  -63,7 +63,11  <at>  <at>
>       (read-line s)))
>   #+unix
>   (defun gsl-config-pathname (pn)
> -    (merge-pathnames pn (pathname (format nil "~a/" (gsl-config
> "--prefix"))))))
> +    (flet ((libpath ()
> +            (let ((s (gsl-config "--libs-without-cblas")))
> +              ;; example output: -L/usr/local/Cellar/gsl/1.16/lib -lgsl
> +              (pathname (format nil "~a/" (subseq s 2 (- (length s)
> 6)))))))
> +      (merge-pathnames pn (libpath)))))
>
> (cffi:define-foreign-library libgslcblas
>   (:darwin #+ccl #.(ccl:native-translated-namestring
>
> If I remember correctly, this was once posted on this mailing list.
>
>>
>> Just to be sure it
>> was installed correctly I ran the following:
>>
>> CL-USER>   (in-package :gsl)
>> #<Package "GSLL">
>> GSL>    (lisp-unit:run-tests)
>> Unit Test Summary
>>  | 3983 assertions total
>>  | 3964 passed
>>  | 19 failed
>>  | 6 execution errors
>>  | 0 missing tests
>>
>> #<TEST-RESULTS-DB Total(3983) Passed(3964) Failed(19) Errors(6)>
>>
>> GSL>
>> --
>>
>> Are these results consistent with expectations or should I be getting
>> no failures or execution errors?
>
>
> I think this is expected, but you should probably check each failure/error
> and decide for yourself whether or not it has an impact on what you want do.
> For example, they may be small numeric inconsistencies that some people care
> and others do not care about.
>
> Regards,
> david.



-- 
Kind Regards
Munawar