good chemistry is complicated,
and a little bit messy -LW
chromatic, thank you for the guidance. Is this process expected to work on Windows XP? I know, I could have tried it myself.
However, being a Windows programmer, I thought that this was as good an occasion as any for me to venture into the Linux world and try perl6 there.
It worked as advertized!
Here are details (yes, brethern in Windows, it was easy):
* downloaded the Ubuntu 7.10 iso image file, made the CD and installed it on an otherwise unused laptop
* downloaded the parrot tarball and extracted it
$ perl Configure.plbut this failed with
Determining what C compiler and linker to use...Compilation failed with 'cc'
* googled, and followed advice found on some forum, to
sudo apt-get install build-essential
$ perl Configure.pl: success
* followed the remaining parrot and perl6 build steps
* sanity test succeeded
And at last, ran my first script
OK, I tried the build process on WinXP + VC8, 32 bit machine, and I got stuck.
First, I had trouble with the old nmake 1.5 which was serving me the error
NMAKE Fatal Error U1095 expanded command line 'commandline' too longAfter some googling I found the solution - use the nmake 8 which comes with VC8
Now the first nmake step worked
The second nmake step
$ nmake -C languages\perl6\was failing, but it worked when I did
cd languages\perl6\ nmakeFor now I am stuck on the third step,
nmake pbc_to_exe- nmake does not know how to make pbc_to_exe.
It is getting late over here, I will need to dig into it tomorrow.
I compared the parrot\makefile generated on Linux with the one on Windows. Well, the Windows makefile does not contain build targets pbc_to_exe and perl6, so that explains my failure to build pbc_to_exe on Windows.
It looks like the feverish activity of parrot porters just before the end of 2007 was limited to the Linux build of perl6, as I guessed, correctly, it turns out.