commit 9cfd094e6d0a842551c1c58e998eb057cd8425e3 Author: H.Merijn Brand <firstname.lastname@example.org> Date: Thu Aug 4 09:20:32 2011 +0200 Support gcc-4.x on HP-UX PA-RISC/64 Correct the socketsize. Probably due to big-endian versus little-endian, this has always worked on Intel CPUs. This is a very very old problem, and it has been the reason I never used gcc-4 on PA-RISC, because perl would not pass the test suite in 64bitall. Noticeable effects of wrong "$socksizetype" are return codes of 0 (pass) from functions like getpeername (), but invalid (or none) data in the returned structures or a return length of 0 or 256. In the latter case, the length is stored in the second part of the 64bit long and the 32bit first part is 0. This might be true on Intel-like machines too, but the tests will pass, as the significant part of the returned length is in the first 32bits and a pointer to int will still see that correct. Mind that in that case the 32bits after that might have been overridden => can of worms.
Since code recently changed from using 0755 to 0644 update the Synopsis Pod accordingly.
… of 755. The 5.13.x branch of perls introduced 'porting/exec-bit.t' which is failing when files that shouldn't have execute bit in the source tree do. Highlighted by Randy Stauner (magnificent-tears) as an issue on Github.
… file didn't get actually patched. Doh.