in reply to Pod-Coverage-0.17 + i686-linux + ErrorCoverage.so: undefined symbol: Perl_Gthr_key_ptr

Sounds like you've got two perls on your system, one threaded, and one unthreaded. And at some point in your execution, the code is pulling in a library that was compiled for the other perl.

Have a look at /usr/bin/perl -V compared to /usr/local/bin/perl -V and see if they are different. Does your Build.PL script start with #! /usr/bin/perl?

• another intruder with the mooring in the heart of the Perl

  • Comment on Re: Pod-Coverage-0.17 + i686-linux + ErrorCoverage.so: undefined symbol: Perl_Gthr_key_ptr

Replies are listed 'Best First'.
Re^2: Pod-Coverage-0.17 + i686-linux + ErrorCoverage.so: undefined symbol: Perl_Gthr_key_ptr
by irfancss (Initiate) on Oct 17, 2005 at 08:27 UTC
    Well I checked that and found they are dirffrent one. But then also its the same problem coming up also the I am using /usr/local/perl for my compilation.
[reply]
      Try starting from a fresh set of sources for the module, and make sure when building it that /usr/local/bin appears in the PATH environment variable before /usr/bin, so that /usr/local/bin/perl is seen first (assuming that /usr/local/bin/perl is the desired Perl you want to compile the module with).
[reply]
        Yes man I did that but no luck.
[reply]

In Section Seekers of Perl Wisdom