summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorSteve Hay <steve.m.hay@googlemail.com>2014-04-14 20:59:44 +0100
committerSteve Hay <steve.m.hay@googlemail.com>2014-04-14 23:15:25 +0100
commit200b4fd964d51e9e061e3425234c5271db3a89b1 (patch)
tree6b6b53cd1b1468f6a2e5dbb8dbd4964eef6e0897 /pod
parent9345802d17d1ff4d7e3651d8701e054f85a5b10a (diff)
downloadperl-200b4fd964d51e9e061e3425234c5271db3a89b1.tar.gz
Set Off_t et al correctly for USE_LARGE_FILES builds on Windows
The canned config files used to build miniperl.exe (with some updates applied by Makefile / makefile.mk) have the non-USE_LARGE_FILES settings for Off_t, LSEEKSIZE and Off_t_size, resulting in an uninitialized memory read in win32_fseek() in miniperl.exe, which recently started causing exetype.pl to write a 4GB wperl.exe during the build of a 64-bit perl. Change Makefile / makefile.mk to use the correct settings for the build of miniperl.exe. This fixes perl #121471.
Diffstat (limited to 'pod')
-rw-r--r--pod/perldelta.pod6
1 files changed, 6 insertions, 0 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index f95219245b..05efcdaec8 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -392,6 +392,12 @@ since the process tree kill feature was implemented on Win32. It has now been
corrected to follow the documented behaviour.
[L<perl #121230|https://rt.perl.org/Public/Bug/Display.html?id=121230>]
+When building a 64-bit perl, an uninitialized memory read in B<miniperl.exe>,
+used during the build process, could lead to a 4GB B<wperl.exe> being created.
+This has now been fixed. (Note that B<perl.exe> itself was unaffected, but
+obviously B<wperl.exe> would have been completely broken.)
+[L<perl #121471|https://rt.perl.org/Public/Bug/Display.html?id=121471>]
+
The test harness now has no failures when perl is built on a FAT drive with the
Windows OS on an NTFS drive.
[L<perl #21442|https://rt.perl.org/Public/Bug/Display.html?id=21442>]