It would indeed surprise me that a low-level routine was actually the root cause of the problem. What usually is the cause is that the list of prerequisites for some (directly or more-likely indirectly included) package is not quite right. A check of the CPAN bug-lists will usually reveal that. In addition, updates that are made to a dependent package without appropriate changes also being made to a module's list of self-tests can cause those self-tests to fail ... leading to this message. Again, by the time you run into glitches like this, you're not gonna be the first to do so. Check bug reports and CPANTS test-logs first.
|Comment on Re: When cpan returns the dreaded "won't install without force"|