Fwd: [mcclim-devel] Re: Beagle backend requirements?

[Duncan Rose]

Begin forwarded message:

> From: Duncan Rose <duncan at robotcat.demon.co.uk>
> Date: Fri Jun 10, 2005  12:16:53  am Europe/London
> To: mcclim-devel at common-lisp.net
> Cc: Brian Mastenbrook <chandler at unmutual.info>, Rainer Joswig 
> <joswig at lisp.de>
> Subject: Re: [mcclim-devel] Re: Beagle backend requirements?
>
>
> Further to this, I can report no problems observed on 10.2 running 
> with OpenMCL 0.14.3 (from the 'distributions' link on Clozure.com, not 
> bleeding edge from CVS or whatever) so I suspect this may be a problem 
> that's specific to Tiger.
>
> Sorry not to be more helpful, but I don't have access to a box running 
> 10.4 :-(
>
> -Duncan
>
>
> On Monday, June 6, 2005, at 12:06  am, Duncan Rose wrote:
>
>>
>> Oops, didn't notice this was posted to the list as well... this is 
>> how I responded to Brian's chandler address:
>>
>> On Thursday, June 2, 2005, at 01:45  am, Brian Mastenbrook wrote:
>>
>>> Hi Duncan,
>>>
>>> What version of OpenMCL is required for running the Beagle backend? 
>>> Right now current CVS won't run on 0.14.3 with an error about ObjC 
>>> ARRAY.
>>>
>>> Should I get bleeding edge or current 0.14 CVS?
>>>
>>
>> I'm currently using the outdated 0.14.1-p1 version, on 10.2
>>
>> I've heard from Rainer Joswig that Beagle doesn't compile under the 
>> latest OpenMCL (but no more than that it fails 'with a type error'; 
>> presumably the same thing you're seeing); there's still quite a lot 
>> of discussion on the OpenMCL list regarding problems with the ObjC 
>> bridge under the latest OpenMCL versions (and I'm pretty sure Jaguar 
>> is not intended to be supported any longer by later OpenMCL versions) 
>> so I haven't done an upgrade (I'm seriously considering forking out 
>> for a new iBook though, at which point I will be upgrading ;-).
>>
>> Could you send me the actual error report? At the moment I'm guessing 
>> from your description that the problem is likely to be in 
>> %COCOA-IMAGE-FROM-PATTERN in OUTPUT;MEDIUM.LISP however I don't 
>> believe any ObjC arrays are used directly by the code (I'm classing C 
>> arrays (char * etc) and ObjC (NSArray) arrays differently, although 
>> perhaps I shouldn't in the context of this issue).
>>
>> -Duncan
>>
>>> Thanks!
>>>
>>>
>>> --
>>> Brian Mastenbrook
>>> http://www.iscblog.info/
>>> http://www.cs.indiana.edu/~bmastenb/
>>>
>>
>> _______________________________________________
>> mcclim-devel mailing list
>> mcclim-devel at common-lisp.net
>> http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel
>>
>