Something is inconsistent: in your previous post you had 

sadm@bioinfo-z:~$ perl -ve
This is perl, v5.8.7 built for sun4-solaris-thread-multi

[download]

and now, you have, apparently under the same circumstances (i.e. same user) 

sadm@bioinfo-z:~$ perl -V
Summary of my perl5 (revision 5 version 8 subversion 4) configuration:
(...)

[download]

(note the different Perl version)

As I said, do try not to mix them up :)   To build an extension for a particular version of Perl, you have to run Makefile.PL with that same version. Perl will then use the configuration belonging to that version to set things up correctly. The easiest way to make sure this happens is to call the desired perl with an absolute path.

(...)
Yes, the same error I have.

Did you in fact call Perl with an absolute path (/home/sadm/.perl/bin/perl Makefile.PL), or just perl Makefile.PL? In case you've actually got the right Perl, you should see "5.8.7" (which I presume is the version in your home) somewhere in the make output.

If you're still having problems with gd.h not being found, do check if it really is readable, e.g. run ls -l /usr/local/include/gd.h as the same user you ran make (and look at the permissions).

If you're absolutely sure the header file is there and readable, but the compiler still won't find it (despite having -I/usr/local/include on its command line), you could use the system call tracer truss to figure out what going on: 

truss -f -t open,stat -o debug.out ...

[download]

where ... is the entire cc command line that is failing (cut-n-paste it as is from the make output). Make sure you run the command from the directory that GD.c is in.

Then inspect debug.out, specifically looking for stuff concerning gd.h (e.g. grep 'gd\.h' debug.out, etc...). This will tell you what paths are being tried, and if the open succeeded. In the latter case you'd see a filedescriptor number, e.g. '= 4' at the end of the line. Otherwise, you'd see the respective error, e.g. Err#2 ENOENT. (It's usually OK to get several errors, as long as at least one attempt to open the file is succeeding...)

Good luck!

In reply to Re^7: Problem installing GD.pm under Solaris by almut
in thread Problem installing GD.pm under Solaris by neversaint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.