No need to change it, just compile it. :)Unfortunately, this is a last-case resort - we have standardised on that particular Perl version, in the documented and tested server builds. Not perhaps the ideal situation - but what's confusing me is that it works on one system, and not the other.
Anything in the logs? Core dumps, anything like that?Nope, no core dumps or anything like that. But interestingly, I think I've narrowed it down a bit. When I ran the tests individually, I could see where they were failing. I then commented out the parts of the test in t/modules/status.t that were failing - and everything passed OK. The relevant code now looks like :-
# removed "hooks" from this one...
my @tests = qw{
script
inc
rgysubs
env
myconfig
};# removed "symdump" from thids one...
push @tests, qw{
inh_tree
isa_tree
} if have_module "Devel::Symdump";I definately have Devel::Symdump, and CPAN informs me it's up to date.
Is that a root prompt? I would always recommend building as an ordinary users and only doing make install as root.
Nope, I build everything as myself, and only use "sudo" to install stuff when necessary.
FWIW, I agree with you - I was just trying out different compilers to eliminate that possibility. I was using GCC 3.2.3, but backtracked to the same compiler used to build Perl, as I recall reading somewhere that doing otherwise can cause some problems. But again, it worked fine one one server - it's just this new "build" server that's causing trouble. What's weird is that everything else builds fine - MySQL, PHP, Apache etc. It's just this Perl build that's giving me hassle...
OK.
Personally I'm tending to go for gcc 3.2.3 at minimum thesedays. Slower by
quite a bit but I feel it's a better compiler. Finds more things wrong. :)
Any further thoughts ?
Thanks,
-Mark
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
