Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: install fails for Inline::C

by Khen1950fx (Canon)
on Mar 13, 2013 at 23:47 UTC ( #1023322=note: print w/replies, xml ) Need Help??

in reply to install fails for Inline::C

I don't think that the problem is with Inline::C. I ran it through automated testing and it passed all tests; however, I noticed that when you try to install Test::Harness, it will fail in the cpan shell but install with a cpan shell script. Here's the cpan shell script that I ran tests on. Give it a test drive:
#!/usr/bin/perl BEGIN { $| = 1; $^W = 1; $ENV{'PERL_MM_USE_DEFAULT'} = 1; $ENV{'MB_TEST_EXPERIMENTAL'} = 1; } use strict; use warnings; use CPAN; CPAN::Shell->install(qw( Exporter Carp XSLoader AutoLoader constant Data::Dumper Scalar::Util Test File::Spec Time::HiRes Pod::Simple Encode Pod::Man ExtUtils::MakeMaker MIME::Base64 Test::Harness Test::More Digest::base Digest::MD5 IO::Handle Text::Balanced SelfLoader File::Temp CPAN CPAN::Meta::YAML version lib ExtUtils::ParseXS Pod::Usage Getopt::Long Text::Abbrev JSON::PP Parse::CPAN::Meta Perl::OSType Locale::Maketext::Simple Module::Load::Conditional Module::Load Params::Check IPC::Cmd File::Path IO::Select Module::Metadata ExtUtils::CBuilder ExtUtils::Manifest CPAN::Meta::Requirements CPAN::Meta ExtUtils::Install PAR::Dist Module::Build Tree::DAG_Node Sub::Uplevel Test::Warn Parse::RecDescent Filter::Util::Call YAML YAML::Syck Inline::Files Inline::C));

Replies are listed 'Best First'.
Re^2: install fails for Inline::C
by Special_K (Beadle) on Mar 14, 2013 at 04:15 UTC

    Khen1950fx: thanks, that seemed to work. What was the problem with the way I was trying to install it? What is your approach doing differently? Also normally when I try to install module I use:

    perl -MCPAN -Mlocal::lib -e 'CPAN::install(<module_name)'

    yet when running your script I apparently didn't need to specify -Mlocal::lib for perl/CPAN to know to install all those modules to my local lib rather than the default location. How did it know about my local lib?

Re^2: install fails for Inline::C
by Anonymous Monk on Dec 04, 2014 at 16:43 UTC
    I would say I had a similar problem, but I read the logs and it turns out I had the exact same problems, without local::lib, it made no difference with or without it. The Inline::C failure was hidden from me just as the previous user and I had to get the test results manually, and of course they were different from the supposed 'summary'. Is there some sort of setting to force the test harness to output ALL the information about the running tests?

      It's unlikely that you would have the same exact failures as what someone else was experiencing six months ago. Inline and Inline::C have undergone a lot of revisions since then, including splitting them into separate distributions.

      Do this: Clone and, each into their own folders, and run make test. This will spit out a more verbose log of test passes/fails. Try this for each of Inline and Inline::C. That should give you a better idea of what is wrong. Feel free to drop by to discuss issues, or open a GitHub issue.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1023322]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (6)
As of 2018-03-24 14:08 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (298 votes). Check out past polls.