It turns out that perlivp has a similar output after a FRESH build of RedHat Linux EL 4 (did a full server rebuild as a last resort). Obviously either perlivp or some of Perl itself is broken on RHEL4, which makes it hard to diagnose if Perl gets really broken by a subsequent module install.

Got a support call in with RedHat for this issue.