Can't locate loadable object for module error

[markmorgan]

I'm getting the following message in XML module GDOME.pm

Can't locate loadable object for module XML::LibXML::Common in @INC (@INC contains: c:/Perl/lib c:/Perl/site/lib .)

I have downloaded Common.pm from CPAN and put it in a directory at C:\Perl\lib\XML\LibXML
Am I missing something obvious in the installation of modules?

Mark.

 

[PaulTEG]

Mark,

How did you install the module, step by step, no assumptions made

--Paul

 

[markmorgan]

To install it I searched for the file on cpan.org. Saved the .pm file to the C:\Perl\lib\XML\LibXML\ (after creating the directory) and ensured that Internet Explorer did not append a .txt extension.

I have since (sending the first mail) discovered the cpan shell utility can be used to install modules. Unfortunately this utility fails complaining that module MM cannot be loaded, although this is in the C:\Perl\lib\ExtUtils directory?

Mark.

 

[Coderifous]

You are on windows. Are you using ActiveState's Perl (ActivePerl)? Try using PPM, the Perl Package Manager that windows users benefit from.

ppm install Bundle::XML
or
ppm install XML::LibXML

The bundle install normally installs a bunch of related modules, making life easy, but there may not be a Bundle::XML, I am just guessing... and am way to lazy to go look.

The manual method you performed is rarely a good idea. There are a couple nice things that a -MCPAN install will do for you, like runt tests. Also, if it's a module that needs compilation, it will attempt that for you. If there are other modules that this module needs before it can work - no problem - it will grab those too! So you can see that just copying the .pm file into place is far less than a typical module installation consists of. There are some modules however, where going totally manual is fine, like File::Slurp for instance. That's a pure-perl module, and I don't believe it depends on anything. Well, it probably does, but my laziness prohibits me from finding a solid example. You get the point I'm sure.

On windows, the -MCPAN method fails miserably often. This is normally thanks to a windows box not having developer tools (like makem, or cc). This can be remedied: Microsoft has released a developer toolkit. There is another post about all of this.

http://www.tek-tips.com/viewthread.cfm?SQID=846389&SPID=219&newpid=219&page=1

Good luck.

--jim

 

[Coderifous]

$last_post =~ s/makem/make (which you'll find is actually nmake)/;