VMs don't compile on Lion

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

VMs don't compile on Lion

Sean P. DeNigris
Administrator
To save Lion users the trouble...

After banging my head against the wall all week at ESUG (thank you Esteban, Igor, and Elliot for all the support), it seems that the Cog family of VMs (tried every variant of Jit/Stack & Carbon/Cocoa) do not compile on OS X Lion. I performed the same steps as both Igor (who succeeded in Snow Leopard) and Jenkins, with errors in during make.
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: VMs don't compile on Lion

Igor Stasenko
 
On 26 August 2011 22:07, Sean P. DeNigris <[hidden email]> wrote:
>
> To save Lion users the trouble...
>
> After banging my head against the wall all week at ESUG (thank you Esteban,
> Igor, and Elliot for all the support), it seems that the Cog family of VMs
> (tried every variant of Jit/Stack & Carbon/Cocoa) do not compile on OS X
> Lion. I performed the same steps as both Igor (who succeeded in Snow
> Leopard) and Jenkins, with errors in during make.
>

Yes, there are some serious troubles with gcc, which simply hangs when compiling
gcc3x-cointerp.c

while works fine on 10.6

So, be warned :)

I am not too hurry with migrating to Lion.. but yes, we have to deal
with this crap sooner or later.

> --
> View this message in context: http://forum.world.st/VMs-don-t-compile-on-Lion-tp3771938p3771938.html
> Sent from the Squeak VM mailing list archive at Nabble.com.
>



--
Best regards,
Igor Stasenko AKA sig.
Reply | Threaded
Open this post in threaded view
|

Re: VMs don't compile on Lion

Lukas Renggli
 
I am not sure if everybody is aware that Apple changed the default compiler in OS X Lion to llvm-gcc-4.2? The same old gcc-4.2 is still available though, you just need to redefine the CC variable. There was a lot of buzz around this when Lion was released, many open source systems have/had problems with the llvm tools.

Luka

On Friday, 26 August 2011, Igor Stasenko <[hidden email]> wrote:
>
> On 26 August 2011 22:07, Sean P. DeNigris <[hidden email]> wrote:
>>
>> To save Lion users the trouble...
>>
>> After banging my head against the wall all week at ESUG (thank you Esteban,
>> Igor, and Elliot for all the support), it seems that the Cog family of VMs
>> (tried every variant of Jit/Stack & Carbon/Cocoa) do not compile on OS X
>> Lion. I performed the same steps as both Igor (who succeeded in Snow
>> Leopard) and Jenkins, with errors in during make.
>>
>
> Yes, there are some serious troubles with gcc, which simply hangs when compiling
> gcc3x-cointerp.c
>
> while works fine on 10.6
>
> So, be warned :)
>
> I am not too hurry with migrating to Lion.. but yes, we have to deal
> with this crap sooner or later.
>
>> --
>> View this message in context: http://forum.world.st/VMs-don-t-compile-on-Lion-tp3771938p3771938.html
>> Sent from the Squeak VM mailing list archive at Nabble.com.
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>

--
Lukas Renggli
www.lukas-renggli.ch
Reply | Threaded
Open this post in threaded view
|

Re: VMs don't compile on Lion

Sean P. DeNigris
Administrator
In reply to this post by Sean P. DeNigris
UPDATE: I successfully compiled the Cog Jit VM on Lion (in Pharo 1.3) with the following:

(ConfigurationOfCog project version: '3.0') load.
CogCocoaIOSConfig generateWithSources.

Note on loading the Metacello project:
    - Wrong way: as Igor mentioned, #latestVersion is *not* a good way to load the Metacello version. In this case it was ~50 versions behind in one package. Ideally, I think this should be updated because Metacello convention is to use #latestVersion (soon to be called #stableVersion), although I realize everyone involved is overworked and this may be too much to ask.
    - Right way: see what version is compatible with your version of the sources by seeing which version is used in codegen-scripts/LoadVMMaker.st

If anyone wants to build the VM before Esteban gets home and checks in his latest changes:
* whenever you get an "error: AGL/gl.h: No such file or directory", go into that source code file and change the directory, so it reads "OpenGL/gl.h"
* for the useTempMem error, see http://forum.world.st/compiling-B3DAcceleratorPlugin-on-Lion-td3704915.html

HTH,
Sean
Cheers,
Sean