Re: Building Parrot on Win32

2001-12-31 Thread Sebastian Bergmann
Gregor N. Purdy wrote: On that last call to nmake, if you get dropped back into Configure.pl, something is wrong configure-wise. I did a fresh CVS checkout just now, and nmake calls Configure.pl again. -- Sebastian Bergmann http://sebastian-bergmann.de/

Building Parrot on Win32

2001-12-30 Thread Sebastian Bergmann
'lo there, just tried to build Parrot 0.3 (from CVS) on Win32 -- but I didn't succeed. The output of perl Configure.pl can be found at http://www.sebastian-bergmann.de/parrot_configure.txt and the output of nmake can be found at

Re: Building Parrot on Win32

2001-12-30 Thread Dan Sugalski
At 09:42 PM 12/30/2001 +0100, Sebastian Bergmann wrote: 'lo there, just tried to build Parrot 0.3 (from CVS) on Win32 -- but I didn't succeed. Argh! Platform quoting issues. Can you edit Makefile and change the appropriate ' to and see how things go from there?

Re: Building Parrot on Win32

2001-12-30 Thread Gregor N. Purdy
Sebastian -- I noticed on your first post of the nmake run log that you ended up re-running Configure.pl. That's not a good sign. I don't know what time you grabbed code from CVS, but if you wouldn't mind doing the following to be *very* sure you've got all the latest checkins, I'd appreciate

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 #

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 Jason Diamond
Hi. snip / 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

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 the

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'll

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