[M3devel] CM3 on Leopard

Tony Hosking hosking at cs.purdue.edu
Mon Jan 7 21:28:59 CET 2008


Very cool!  I was thinking it was going to be more painful.  Have you  
bootstrapped a new compiler?


On Jan 7, 2008, at 3:23 PM, Darko wrote:

> It seems that I just forgot to install the latest tools. I fixed it  
> by installing XCode from the Leopard DVD.
>
> Exceptions seem to work ok, but I did a very basic test. Maybe I  
> can run the regression test suite on 10.5 when it's finished. I'll  
> report any problems meanwhile.
>
> Thanks,
> Darko.
>
>
>
> On 07/01/2008, at 11:08 AM, Tony Hosking wrote:
>
>>
>> On Jan 7, 2008, at 1:12 PM, Darko wrote:
>>
>>> Hi Tony,
>>>
>>> Are you using CM3 on Leopard, aka Mac OS X 10.5?
>>
>> No, I've deliberately *not* upgraded to Leopard until I am able to  
>> test CM3 on it.  Generally, I avoid bleeding edge OS upgrades for  
>> precisely this reason.  I don't know when I will have time to play  
>> with CM3 on Leopard.  Right now, I am tracking down another issue  
>> related to the regression framework Olaf is putting together.
>>
>>> It's stopped working since I upgraded, I get:
>>>
>>> cc -o parser -fPIC  _m3main.o [ ... various libs, modules ... ] - 
>>> lm3gcdefs -lm -multiply_defined suppress -bind_at_load -shared- 
>>> libgcc
>>
>> At least this suggest your cm3 binary was able to run on Leopard,  
>> which is a good start.
>>
>>>
>>> /usr/bin/ld: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../ 
>>> libm.dylib unknown flags (type) of section 6  
>>> (__TEXT,__dof_plockstat) in load command 0
>>> /usr/bin/ld: can't locate file for: -lgcc_s.10.4
>>> collect2: ld returned 1 exit status
>>>
>>> when trying to compile. Uname says:
>>>
>>> Darwin Lucifer.local 9.1.0 Darwin Kernel Version 9.1.0: Wed Oct  
>>> 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386 i386
>>>
>>> It would seem that i just needs to be nudged up to the right  
>>> version, but I couldn't find anything in the cfg file. Any  
>>> suggestions?
>>
>> I suspect that you need to rebuild the m3cg backend, but I have no  
>> idea how well it will play with Leopard.
>>
>> Also, I have heard there were changes to ucontexts and other  
>> thread state which may mean M3 exceptions break, but I have not  
>> verified yet.
>>
>>>
>>> Thanks,
>>> Darko.
>>>
>>




More information about the M3devel mailing list