vikram1974 has asked for the wisdom of the Perl Monks concerning the following question:

hi,
I am trying to install Proc::ProcessTable using CPAN dlv-mplus-w003 mnpEfmEngine/bin% uname -a Linux dlv-mplus-w003 4.4.103-92.56-default #1 SMP Wed Dec 27 16:24:31 +UTC 2017 (2fd2155) x86_64 x86_64 x86_64 GNU/Linux perl version = v5.18.2 Error ========= cpan[1]> install Proc::ProcessTable Reading '/appl/mamon/.cpan/Metadata' Database was generated on Mon, 12 Mar 2018 18:41:02 GMT Running install for module 'Proc::ProcessTable' Running make for J/JW/JWB/Proc-ProcessTable-0.55.tar.gz Checksum for /appl/mamon/.cpan/sources/authors/id/J/JW/JWB/Proc-Proces +sTable-0.55.tar.gz ok Scanning cache /appl/mamon/.cpan/build for sizes ...................................................................... +......DONE CPAN.pm: Building J/JW/JWB/Proc-ProcessTable-0.55.tar.gz Checking if your kit is complete... Warning: the following files are missing in your kit: TODO Please inform the author. Processing hints file hints/linux.pl Writing Makefile for Proc::ProcessTable::Process Writing MYMETA.yml and MYMETA.json Writing Makefile for Proc::ProcessTable Writing MYMETA.yml and MYMETA.json cp Killall.pm blib/lib/Proc/Killall.pm cp Killfam.pm blib/lib/Proc/Killfam.pm cp ProcessTable.pm blib/lib/Proc/ProcessTable.pm cp example.pl blib/lib/Proc/example.pl make[1]: Entering directory '/appl/mamon/.cpan/build/Proc-ProcessTable +-0.55-PCGf0t/Process' cp Process.pm ../blib/lib/Proc/ProcessTable/Process.pm AutoSplitting ../blib/lib/Proc/ProcessTable/Process.pm (../blib/lib/au +to/Proc/ProcessTable/Process) Manifying ../blib/man3/Proc::ProcessTable::Process.3pm make[1]: Leaving directory '/appl/mamon/.cpan/build/Proc-ProcessTable- +0.55-PCGf0t/Process' /usr/bin/perl /usr/lib/perl5/5.18.2/ExtUtils/xsubpp -typemap /usr/lib +/perl5/5.18.2/ExtUtils/typemap ProcessTable.xs > ProcessTable.xsc && + mv ProcessTable.xsc ProcessTable.c cc -c -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -fno-strict- +aliasing -pipe -fstack-protector -D_LARGEFILE_SOURCE -D_FILE_OFFSET_B +ITS=64 -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 + -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tabl +es -g -Wall -pipe -DVERSION=\"0.55\" -DXS_VERSION=\"0.55\" -fPIC "- +I/usr/lib/perl5/5.18.2/x86_64-linux-thread-multi/CORE" ProcessTable +.c /bin/sh: cc: command not found Makefile:353: recipe for target 'ProcessTable.o' failed make: *** [ProcessTable.o] Error 127 JWB/Proc-ProcessTable-0.55.tar.gz /usr/bin/make -- NOT OK 'YAML' not installed, will not store persistent state Running make test Can't test without successful make Running make install Make had returned bad status, install seems impossible Failed during this command: JWB/Proc-ProcessTable-0.55.tar.gz : make NO Appreciate your help

Replies are listed 'Best First'.
Re: install Proc::ProcessTable in Linux
by roboticus (Chancellor) on Mar 12, 2018 at 19:50 UTC

    vikram1974:

    The error "/bin/sh: cc: command not found" indicates that either you don't have a C compiler installed on the machine, or that your account isn't set up to use it. Try resolving that and then try installing Proc::ProcessTable again.

    ...roboticus

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

      gcc compiler is already there, how to make point cc=gcc to proceed? Thanks
        gcc compiler is already there, how to make point cc=gcc to proceed?

        It shouldn't be necessary to do that, and I think the advice offered by roboticus is sound.

        However, to answer your question:
        cpanm Proc::ProcessTable --configure-args="cc=gcc"
        or, if gcc location is not in $PATH environment variable:
        cpanm Proc::ProcessTable --configure-args="cc=/full/path/to/gcc"
        Cheers,
        Rob

        vikram1974:

        Talk with your system administrator who can help you get your shell profile set up appropriately.

        Usually, you need to verify that your account has appropriate permissions to access/execute the files (the compiler, linker, libraries, include files, etc.), and that your shell configuration sets up the environment variables for you.

        ...roboticus

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