Steve Hay wrote:

>Arthur Bergman wrote:
>
>  
>
>>This is Ponie, development release 2
>> 
>>
>>    
>>
>How does one build this on Win32 with MSVC++?
>
>Running the top-level "perl Configure.pl" got me nowhere, so I cd'd into 
>parrot and ran "perl Configure.pl" there.  That ran OK, so I tried 
>"nmake" next.
>
>It almost worked.  The compiler complained a couple of times about 
>struct tm being undefined; I included <time.h> in a couple of places and 
>those errors went away.  libparrot_s.lib was then linked successfully, 
>but linking parrot.exe fell over with three unresolved externals: 
>asctime_r, gmtime_r and localtime_r.  These are not present in the VC++ 
>header files.
>
OK, I've got parrot built now by using the latest CVS version which 
fixes those problems.

How do I do the rest of what the top-level Configure.pl would have 
done?  The README says to "reconfigure perl with all the correct 
settings", but I don't know what that means.

Looks like that Configure.pl runs perl's "Configure" shell script with a 
bunch of arguments pulled from various sources, but on Win32 you don't 
use that Configure script to build perl -- instead, you edit 
win32/Makefile to suit, then cd to win32/ and type "nmake".

So I guess the question is: What do I need to do to win32/Makefile to 
have perl built with parrot?

- Steve



------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are 
confidential and intended for the addressee(s) only.  If you have received this 
message in error or there are any problems, please notify the sender immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is strictly 
forbidden.  Note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of Radan Computational Ltd.  The 
recipient(s) of this message should check it and any attached files for viruses: Radan 
Computational will accept no liability for any damage caused by any virus transmitted 
by this email.

Reply via email to