In my present work situation, I find myself in the position that I can only use CPAN modules which are pure perl. I am not in a position to be able to build any perl extensions.
I can see that this might occur as a result of several things:
- Lack of a C compiler
- Lack of a C compiler that is capable of building perl (several Unixes ship with a non-ANSI ucb flavour of cc, MSVC on Win32 requires some setting up to make it usable)
- Perl was built on a different machine, with a config which is not available on the target machine
So, why not build a new perl from scratch – and use this as a basis? Well, this raises the issues of deploying a new build of perl – change management or the ISP may not agree (the change management issue is what is stopping me).
What I am really after is a way of filtering the CPAN search, so that it only selects modules which are pure perl, requiring no extensions to be built for installation. In my case, I am building modules by hand.
I am also interested in a way of determining up-front, whether building of extensions is required, so as to save me the hassle and waste of time of attempted and failed builds, when a vital component is XS.