Re^2: module errors everywhere

From the documentation:

unknown [...]
The domain has a configuration error in the published data or defines a mechanism that this library does not understand. If the data contained an unrecognized mechanism, it will be presented following "unknown". You should test for unknown using a regexp /^unknown/ rather than eq "unknown".

So I'd suggest checking checking the configuration of your server (if you control it) or contacting the sysadmin to find out if there are any configuration problems. If it's operating correctly and you're getting unknown then it doesn't look like you'll be able to use the module, as it apparently doesn't support the feature, or has an unsupported policy set up.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

Comment on Re^2: module errors everywhere Select or Download Code

Replies are listed 'Best First'.
Re^3: module errors everywhere by Toasterman (Novice) on Aug 06, 2014 at 18:34 UTC
Thank you, but I'm as close to a sysadmin as this place has and I'm not aware of any configuration problems. I had this installed on my system perl just fine by using the CentOS repository package. Why would it work on a different location on the same system?	[reply]
Re^4: module errors everywhere by roboticus (Chancellor) on Aug 06, 2014 at 21:37 UTC
Toasterman: Good question. The only thing I can think of are differences in: directory permissions for the various include directories environment variables (e.g., PERL5LIB pointing into the "old" perl) ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply]