On Sat, Mar 08, 2008 at 08:55:36PM +0100, Reini Urban wrote: > Still doing cygwin testing. Thanks for doing this. > So far I have these 5.8.9 failures: > ../ext/Time/HiRes/t/HiRes.t 0 15 38 0 ?? > ../lib/CPAN/t/10version.t ?? ?? ?? > ../lib/ExtUtils/t/Constant.t 272 271 2-272 > ../lib/ExtUtils/t/FIRST_MAKEFILE.t 2 512 7 2 4-5 > ../lib/ExtUtils/t/INSTALL_BASE.t 16 4096 21 16 4-19 > ../lib/ExtUtils/t/basic.t 69 17664 83 69 4 6-55 57-59 > 61-67 69 > 71-74 77 80-81 > io/tell.t 28 1 28 I assume (hope) that the ExtUtils tests pass hen ExtUtils::Install 1.50 is merged, although the failure of Constant.t may not be related Do all tests pass on the same setup with blead? > But I have some minor cygwin improvements, > which should in the upcoming cygwin release also: > ----- > > * Update README for the ld2 axe, and a bit more. > > * CYG04 At least on cygwin strip the last number > from the dll. This is in the cygwin.com build since years. None of these changes are in blead. Assuming that they are relevant to 5.11, 5.10.1-tobe and 5.8.9-tobe, should I just apply them there and merge them across? Also, is it right to do this within the 5.8.x branch? +# added -mms-bitfields to be able to link to MSVC win32 bitfields libs +# (4 byte instead of 2 byte alignment) $spitshell >>Makefile <<!GROK!THIS! LIBPERL = $libperl @@ -42,6 +50,7 @@ DLLNAME= $dllname CLDFLAGS= -L$addtopath $ldflags LDDLFLAGS = --shared -L$addtopath $ldflags +CCFLAGS=$ccflags -mms-bitfields PLDLFLAGS = CAT = $cat AWK = $awk specifically, it will act as a binary compatibility breakage between 5.8.8 and 5.8.9, won't it? The changes that prompted this (to structure members of op.h) didn't (can't) go back into 5.8.x, so is it needed? > * CYG01 update hints from blead I'll just merge that from blead then. > * CYG09 enhance GetCurrentThreadId test This is appropriate for blead and 5.10.x too? > * CYG10 improve Win32::GetLastError test And this? Nicholas ClarkThread Previous | Thread Next