Joop,
I decided to try again. I have a couple questions:
1) how do I know that the 'automatic' installs are installing the
latest versions of perl, SearchBuilder, etc.?
2) What am I really supposed to do with this result?
The automatic tests for GDGraph are not really a solid workout of the
library. The best way to test the package is to run the examples
before installing it. You can run the examples in the samples
directory with `make samples` or by going into that directory, and
just running `make`.
If that fails, please read samples/Makefile.
---- Unsatisfied dependencies detected during ----
---- BWARFIELD/GDGraph-1.44.tar.gz ----
GD::Text [requires]
Shall I follow them and prepend them to the queue
of modules we are processing right now? [yes]
Do I stop the 'make fixdeps' and run the 'make samples' (where IS the
samples directory anyway)?
Kenn
LBNL
On 10/9/2008 10:41 AM, Joop van de Wege wrote:
> Kenneth Crocker wrote:
>> Any clues as to why the "C" compiler is needed? Thanks.
> Not all Perl modules are Pure Perl modules which means that for example
> GD has a Perl interface to the gd.so which fixdeps will try to compile
> for you.
> That is probably not the right thing to say but I hope its close enough
> for you to understand the why of th C compiler.
>
> If you really get stuck I might be able to help out, since we used to be
> quite involved with Sun Solaris.
>
> Joop
>
>
>
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
