RE: Building Parrot for Win32.

2001-11-01 Thread Brent Dax
Jason Diamond: # > # Once I got past that, it couldn't link to # classes/intclass.obj. After # > # looking at the output a bit, I found out that intclass.obj is # > # being written # > # to the main parrot directory and not into the classes # > # directory. The option # > # for CL to specify the o

RE: Building Parrot for Win32.

2001-11-01 Thread Gregor N. Purdy
Brent (and Jason) -- Based on Dan's agreement to the approach, I just checked in the starting point files for doing this "right". Please have a look and send patches against those files. As soon as we get config wired up to autoselect the appropriate platform files, we'll be able to make this All

RE: Building Parrot for Win32.

2001-11-01 Thread Gregor N. Purdy
Dan -- > platform.c and platform.h is exactly what we're going to do. We need a > platforms directory as well. In there we'll have a win32.[ch], a > linux.[ch], a vms.[ch], a generic.[ch] and so on. Configure.pl will copy > the appropriate ones up and rename them platform.c & platform.h, and we'

RE: Building Parrot for Win32.

2001-11-01 Thread Dan Sugalski
On Thu, 1 Nov 2001, Gregor N. Purdy wrote: > 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 th

Re: Building Parrot for Win32

2001-11-01 Thread Jason Diamond
Hi. > in /usr/include/sys/stat.h. As for what to includ in Windows to get > these (if anything), or what should be done to get them, I'm unsure. > I suppose for now, you could paste the above into a header file > somewhere with a #ifdef WIN32 around it to get things compiling. I'd suspect that

RE: Building Parrot for Win32.

2001-11-01 Thread Gregor N. Purdy
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

Re: Building Parrot for Win32

2001-11-01 Thread Gregor N. Purdy
Jason -- > I'm trying to build parrot on my Windows 2000 box and am failing when > compiling core_ops.c with these errors: > > core_ops.c(370) : error C2065: 'S_IRUSR' : undeclared identifier > core_ops.c(370) : error C2065: 'S_IWUSR' : undeclared identifier > core_ops.c(370) : error C2065: 'S_

RE: Building Parrot for Win32.

2001-11-01 Thread Brent Dax
Jason Diamond: # > Can you give me the output of that time.c compilation? Someone just # > asked for feedback on how that was working. # # It was complaining about SYSTEMTIME not being defined. You # have to #include # for that. But that caused a redefinition error # for BOOL. So I # renamed the

RE: Building Parrot for Win32.

2001-11-01 Thread Brent Dax
Jason Diamond: # I'm having trouble building the latest parrot sources from # CVS on Windows # 2000. The Configure.pl script ran fine but after running # nmake test_prog.exe # I'm getting an error while compiling core_ops.c: # # core_ops.c(370) : error C2065: 'S_IRUSR' : undeclared identifier # co