Front page | perl.perl5.porters |
Postings from January 2005
I currently have a bunch of tests in lib/Config/Extensions.t failing on Win32: not ok 11 - Encode::Byte was built not ok 17 - Errno was built not ok 21 - Encode::EBCDIC was built not ok 39 - Encode::CN was built not ok 65 - Encode::JP was built not ok 69 - Encode::KR was built not ok 71 - Encode::TW was built not ok 75 - Encode::Symbol was built These are the tests relating to the "nonxs_ext" extensions, and they are failing because they are genuinely not listed in "extensions". From my Config_heavy.pl: dynamic_ext='Storable Encode XS/Typemap MIME/Base64 IO B/C Devel/Peek Time/HiRes Opcode attrs PerlIO/scalar ByteLoader Unicode/Normalize re B XS/APItest Encode/Unicode SDBM_File PerlIO/via PerlIO/encoding Fcntl Sys/Hostname Digest/MD5 Devel/PPPort POSIX Filter/Util/Call Socket threads/shared Data/Dumper threads List/Util File/Glob Devel/DProf Cwd' nonxs_ext='Encode/TW Encode/Byte Errno Encode/KR Encode/EBCDIC Encode/JP Encode/Symbol Encode/CN' static_ext='' extensions='Storable Encode XS/Typemap MIME/Base64 IO B/C Devel/Peek Time/HiRes Opcode attrs PerlIO/scalar ByteLoader Unicode/Normalize re B XS/APItest Encode/Unicode SDBM_File PerlIO/via PerlIO/encoding Fcntl Sys/Hostname Digest/MD5 Devel/PPPort POSIX Filter/Util/Call Socket threads/shared Data/Dumper threads List/Util File/Glob Devel/DProf Cwd' What's wrong here? Should the "nonxs_ext" extensions be listed in "extensions", or should Extensions.t not be testing for that? It sounds like the former to me (from looking at the description of "extensions" in lib/Config.pod), but I'm not sure how to make that happen. - Steve ------------------------------------------------ Radan Computational Ltd. We would like to take this opportunity to wish all our customers, suppliers and colleagues seasons greetings. We will not be sending corporate greetings cards this year. Instead, we will be making a donation to charity. 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.Thread Next