Steve Peters wrote:

On Sat, Sep 24, 2005 at 12:45:35PM +0100, Nicholas Clark wrote:
On Fri, Sep 23, 2005 at 09:14:09PM +0100, Nicholas Clark wrote:
And between last time and this one I didn't think that there were any
dangerous changes. Given that, and the lack of any helpful log on this
smoke report, I'm stuck as to what I messed up that needs fixing.
I think I failed to spot a change that I needed to integrate. Hopefully 25592 fixes it. I think that Steve Hay's 5.8.7 smoker only works weekdays,
so if someone else is able to test build maint on Windows I'd be most
grateful.


I pulled down a perl-5.8.x at 25596, and it built just fine on Win32. There does seem to be a bit of a problem with the Win32 Makefile, though.
Several files are getting getting compiled twice.  What happens is all the
files that do not dependin on the Win32 config.h are built.  conofig.h is
created and the rest of the core files are built.  Then, config.h is recreated
forcing a recompile of all the files that depend on config.h.

There's nothing wrong here (other than (possibly) the overall design of the build process on Win32).

What happens is that the core C files are compiled once using one of the canned config.h files (config.vc et al) found in win32/. These are used to link a miniperl.exe. This is then used to write a real config.h based on the actual configuration choices made in the Makefile. After that, all the core C files are recompiled and used to link perl.exe.



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