On Tue, Jul 2, 2013 at 8:14 AM, Nicholas Clark <nick@ccl4.org> wrote: > nonxs_ext (Extensions.U): > - This variable holds a list of all non-xs extensions included > - in the package. All of them will be built. > + This variable holds a list of all non-xs extensions built and > + installed by the package. By default, all non-xs extensions > + distributed will be built, with the exception of platform-specific > + extensions (currently only one VMS specific extension). This statement is true for non-VMS platforms, but there is a potential confusion here in that VMS::Filespec is an XS extension on VMS (with the XS bits living in vms/vms.c), but if you attempt to use it on another platform, you get (very out-of-date) pure-Perl overrides. > I don't think that this RT can be considered resolved until configure.com has > been updated to be consistent with Configure. Working on it. My initial attempt put VMS::Filespec in nonxs_ext, which I think made it get the wrong arguments to TestInit.pm (in any case the test failed). It doesn't really belong in dynamic_ext since it's not dynamic, nor does it really belong in static_ext since it's not built the way a statically linked extension would be. For now, keeping it out of nonxs_ext is probably good enough. Until it got moved to ext/, it didn't appear in any of the lists, not even known_extensions.Thread Previous | Thread Next