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

Dear Wise monks,
I need some help with installing and running graphviz on my linux box. My distribution is CentOS 5. I installed graphviz via 'yum install*'. That was successful. But I have not been unable to run my perl scripts off it. This is usually the error report I get:

Can't locate graphviz.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at trygraph.pl line 6.

I find that I am also unable to locate graphviz.pm. I have also installed the perl-GraphViz module, even though I thought it was contained in the initial installation. But it has been unsuccessful. I suppose there is something that I have not yet got quite right and would be happy if anyone can point me in the right direction. Thanks
  • Comment on Problems running graphviz after installation

Replies are listed 'Best First'.
Re: Problems running graphviz after installation
by marto (Cardinal) on Feb 07, 2011 at 15:00 UTC

    Such things are case sensitive, you seem to have use graphviz; when you should have use GraphViz;.

Re: Problems running graphviz after installation
by toolic (Bishop) on Feb 07, 2011 at 15:01 UTC
    Can't locate graphviz.pm in @INC
    Could it be as simple as using the proper case? Perl is case-sensitive, as the GraphViz SYNOPSIS shows:
    use GraphViz;
    I find that I am also unable to locate graphviz.pm.
    This script can be used to locate all .pm files in your @INC directories. It uses regular expressions, so you don't have to know the exact name or case:
    findpm -p graphviz
      Thank you so very much. Your post was very useful. It also turned out that I had used the wrong case. Once more thanks.
      Thank you so very much. Your post was very useful. It also turned out that I had used the wrong case. Once more thanks.