Windows VM with latest MinGW: time_t issues

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

Windows VM with latest MinGW: time_t issues

philippeback
 
I have been attempting to build the Windows VM with the latest MinGW.

Compared to my earlier attempts, I now got all plugins to build properly (error was due to a faulty download from files.pharo.org).

Now, there is that message at link time that complains about time_t not being 32 bit (runtime message issued from Pharo.exe).

Well, in 2013, time_t should be 64 bit, we'll have to look into that.

I am trying to build with an additional -D_USE_32BIT_TIME_T to see if that changes anything.

Anyone having had a look in these things?

TIA
Phil
Reply | Threaded
Open this post in threaded view
|

Re: Windows VM with latest MinGW: time_t issues

philippeback
Good news, I was able to get the full thing to build by adding the -D_USE_32BIT_TIME_T to CMakeLists.txt int he pharo-vm\build\ folder.

Pharo.image opens without problem.

Tests are fine, except ZdcSecureSocketStreamTests>>testIsNativeSSLPluginPresent

looks like primitive 'primitiveCreate' in module 'SqueakSSL' is missing.

But the plugin has been built.

Well, that's already much further :-)

Phil
Reply | Threaded
Open this post in threaded view
|

Re: Windows VM with latest MinGW: time_t issues

philippeback
I have been making a change to the code  (small thing, printf inside tryLoading of ioLoadModule) and recompiled all (make).

And now, the plugin loads... BTW, there is a lot of tryLoading even for internal modules it seems.

Interesting to see that printf has been redirected to the console down the host window. Didn't expected that.