<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 23, 2009, at 13:00, David Silva wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thank you guys, it seems that i didn't had installed GCC, and now there is another error after i run the comand : <br># <a href="http://catalyst.pl">catalyst.pl</a> Myapp<br>Can't locate Class/MOP.pm in @INC<br></blockquote><div><br></div><div>It appears to me that the catalyst script cannot find the Class::MOP module in your perl module path, known as @INC. Since @INC is a regular perl array, you can search through it to see the locations of where your perl modules are stored:</div><div><br></div><div>perl -e 'print map { $_ . "\n" } @INC'</div><div><br></div><div>Which on my system produces: </div><div><br></div><div><div>/etc/perl</div><div>/usr/local/lib/perl/5.10.0</div><div>/usr/local/share/perl/5.10.0</div><div>/usr/lib/perl5</div><div>/usr/share/perl5</div><div>/usr/lib/perl/5.10</div><div>/usr/share/perl/5.10</div><div>/usr/local/lib/site_perl</div><div>.</div><div><br></div></div><div>Here's a perl script that prints out the versions of modules you have installed on your system, this might be useful for finding Class::MOP;</div><div><br></div><div><div>#!/usr/bin/perl</div><div><br></div><div>use ExtUtils::Installed;</div><div>my $instmod = ExtUtils::Installed->new();</div><div>foreach my $module ($instmod->modules()) {</div><div> my $version = $instmod->version($module) || "???";</div><div> print "$module -- $version\n";</div><div>}</div><div><br></div><div>Now you can double check to see if you have in fact installed Class::MOP and if not, install it via cpan or your package management tool. You may also consider following Octavian's good advice from a previous email to this thread.</div><div><br></div><div>Note that if you install modules with the cpan tool, it installs perl modules in a pre-determined location (you can change this of course), but that location is not the same location that your package management system or Vendor may choose to install modules. That is why it is important you mention which OS you are on and if you are installing modules using cpan, cpanplus or apt-get for example. At this point I will make a quick plug for debian since there are a few of us in the debian perl group who are determined to make installing catalyst on debian as painless as possible. Catalyst also provides excellent documentation, including installing catalyst on debian.</div><div><br></div><div>Regards,</div><div><br></div><div>Jeremiah</div><div><br></div></div><blockquote type="cite"><div class="gmail_quote"> <br>This is the module Class::MOP ? If it is it gives me another error ... (after alot of text)<br><br><blockquote>t/315_magic.t (Wstat: 512 Tests: 0 Failed: 0)<br> Non-zero exit status: 2<br> Parse errors: Bad plan. You planned 9 tests but ran 0.<br> t/500_deprecated.t (Wstat: 512 Tests: 0 Failed: 0)<br> Non-zero exit status: 2<br> Parse errors: Bad plan. You planned 6 tests but ran 0.<br>Files=77, Tests=22, 6 wallclock secs ( 0.29 usr 0.16 sys + 5.26 cusr 0.79 csys = 6.50 CPU)<br> Result: FAIL<br>Failed 74/77 test programs. 2/22 subtests failed.<br>make: *** [test_dynamic] Error 2<br> DROLSKY/Class-MOP-0.93.tar.gz<br> /usr/bin/make test -- NOT OK<br>//hint// to see the cpan-testers results for installing this module, try:<br> reports DROLSKY/Class-MOP-0.93.tar.gz<br>Running make install<br> make test had returned bad status, won't install without force<br></blockquote>Thank you for your help once more!<br><br>2009/9/22 Octavian Râsnita <span dir="ltr"><<a href="mailto:orasnita@gmail.com">orasnita@gmail.com</a>></span><br> <blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; position: static; z-index: auto; ">From: "Alejandro Imass" <<a href="mailto:alejandro.imass@gmail.com" target="_blank">alejandro.imass@gmail.com</a>><div class="im"> <br> Here is how I go about with a CPAN failed test:<br> 1) Determine which module is producing the error. This is usually as<br> easy as scrolling up a bit in your shell and look for the latest lines<br> that read "Going to build XXX".<br> 2) Exit the CPAN shell and go to the build directory, which would be<br> ~/.cpan/build/module-XXXX . You have to be careful that XXXX is the<br> actual version you are trying to install. If unsure delete all<br> versions of the module there (rm -Rf ~/.cpan/build/module*) and re-try<br> with CPAN shell. If you are probably runing CPAN as root, that would<br> be /root/.cpan/build/module-XXXX.<br> 3) Inside the directory of the module, just run make and make test and<br> try to see exactly what's going on. Usually is a failed dependency<br> like Tom said, but sometimes it may be things like your locale or many<br> other things. If unsure, just copy the ouput from that single module's<br> output here and many will surely help.<br> Best,<br> Alejandro Imass<br> <br></div> If you want to go into the directory where the module ModuleName was built, you don't need to exit the CPAN shell, but just use:<br> <br> cpan> look ModuleName<br> <br> It will open a sub-shell.<br> There you can use perl Makefile.PL, make, make test, prove -l t<br> Then you can go back to the cpan shell by using exit command.<br> <br></blockquote></div></blockquote></div><br></body></html>