On Wed, Jul 11, 2012 at 09:49:18PM +0100, Nicholas Clark wrote: > You're never going to fix version.pm with this, because parts of it are > hard coded into util.c. Sorry. > > (But if it *is* possible to kick parts of util.c out into XS code, then > it may well be possible to fix how we handle version.pm without changing the > build system at all) Right. version::vpp provides a pure perl emulation of some of version, doesn't it? I see that it wants to use POSIX for locale_h. As an experiment, if that's patched to remove that code (assume that it's the "C" locale), and util.c is patched to remove all the version:: XS code (ie #if 0/#endif), is version::vpp good enough for miniperl to be able to get through the entire build process until the build process wants to run ./perl ? (It's permissible to do evil in lib/buildcustomize.pl such as loading modules and alias symbol tables. That has almost complete control over what miniperl actually ends up being when it actually gets to run the real script.) Because if that's a yes, then there looks like a route to getting all of version.pm/version.xs etc into cpan/, and that painful can of worms squished. (Note that it's quite possible for the core to ship and use code internally that it doesn't install) Nicholas ClarkThread Previous | Thread Next