Brent --

[ snip Jason Diamond's question ]
 
> No, this seems to be a case of Unix-centrism.  (I feel your pain--I'm on
> Win32 too.)  I'm CCing perl6-internals on this, since I don't really
> have the C experience to know what to do here.

I just posted a reply to someone else on the matter. If someone takes that
and gets things working, I'll accept a patch to make it work for you guys.
 
> In the mean time, if you really want to build Parrot *right now* and
> don't care about the file I/O ops, you can comment out lines 143 and 148
> in the 'core.ops' file and rebuild to get rid of this error.  However,
> there are several other known Win32 build issues, so you'll likely have
> to fiddle with things to get them to work.  (The sleep() op is another
> source of such misery.)

We need to make a Parrot_sleep wrapper that for *nix does what we do now
and for Win32 does (a) nothing or (b) waves the entrails correctly to get
Win32 to sleep for N seconds. Patches encouraged, as always.

We may end up needing to consolidate these platform-isms into a small
number of files (one?) rather than have them split by type (like I did for
Parrot_*_time). I don't know if we can get away with something as simple
as platform.[hc] with all the yuck in one place or whether we need to have
a platform/ directory with platform_*.[hc] in it that get copied at config
time to platform.c and include/parrot/platform.h...


Regards,

-- Gregor


Reply via email to