[Openmcl-devel] Re: [Bug-openmcl] todo for 0.14.4

alex crain alexcrain at mail.widgetworks.com
Fri Aug 12 06:09:16 PDT 2005


On Aug 12, 2005, at 2:38 AM, Gary Byers wrote:

>
>
> On Thu, 11 Aug 2005, alex crain wrote:
>
>
>>
>> The ccl tree is the bleeding edge distribution as of a couple of  
>> days ago.
>> built and dumped for the G4/Tiger environment. If you want to run  
>> under panther,
>> you'll need to recompile the kernel and make new fasl files.
>>
>>
>
> Why is it necessary to recompile the kernel and make new fasl files in
> order to run under Panther ?

Actually, I don't have a convenient test bed for panther, and simply  
assumed that
Tiger binaries would not be backward compatible. I should have said:

    Platforms that will not run a tiger binary will need to be  
recompiled. Here are
    the instructions ....

I was just trying to be concise, in case anybody actually needed to  
do that.

> That -sounds- like it may be a LaunchServices caching issue (or  
> something
> similar), and offhand it sounds a little surprising if recompiling  
> things
> fixed it (unless doing so had the side-effect of updating that cache.)
>
> Is there another (better) explanation ?

My apologies. I did not mean to suggest that recompiling would fix  
any problems
with the application, sorry.

I don't think that I had to do anything to the Hemlock code to make  
it work under
Tiger when I upgraded, so I was actually hoping that it would work  
out of the box
on pre-tiger OS versions.

I'll see if I can find a Panther machine to play with and fix it over  
the weekend.




More information about the Openmcl-devel mailing list