thanks...I installed an upgraded libgd via ipkg (a packet management system) and that particular error has gone. There are NO errors or clues during 'make'. But 'make test' still fails
in particular, the found gd.h header file in /usr/includegd.h !!warning!! persists
[/share/MD0_DATA/.cpan/build_dir/GD-2.46-hg6AiN] perl Makefile.PL
Notice: Type perl Makefile.PL -h for command-line option summary.
Configuring for libgd version 2.0.35.
Checking for stray libgd header files...
** WARNING: found gd.h header file in /usr/includegd.h, but it is expe
+cted at /opt/include/gd.h. This may cause compile errors! **
** WARNING: found gd.h header file in /usr/includegd.h, but it is expe
+cted at /opt/include/gd.h. This may cause compile errors! **
** Possible problems found **
Included Features: GD_JPEG GD_FONTCONFIG GD_FREETYPE GD_PNG G
+D_GIF GD_GIFANIM GD_OPENPOLYGON GD_UNCLOSEDPOLY
GD_ANIMGIF GD_FTCIRCLE VERSION_33
GD library used from: /opt
Checking if your kit is complete...
Looks good
Writing Makefile for GD
Writing MYMETA.yml
Then:
[/share/MD0_DATA/.cpan/build_dir/GD-2.46-hg6AiN] # make
/share/MD0_DATA/.qpkg/Optware/bin/perl GD/Image.pm.PLS GD/Image.pm
Extracting Image.pm (with variable substitutions)
cp GD/Polyline.pm blib/lib/GD/Polyline.pm
cp qd.pl blib/lib/qd.pl
cp GD/Image.pm blib/lib/GD/Image.pm
cp GD.pm blib/lib/GD.pm
AutoSplitting blib/lib/GD.pm (blib/lib/auto/GD)
cp GD/Simple.pm blib/lib/GD/Simple.pm
cp GD/Polygon.pm blib/lib/GD/Polygon.pm
cp GD/Group.pm blib/lib/GD/Group.pm
/share/MD0_DATA/.qpkg/Optware/bin/perl /opt/lib/perl5/5.14.2/ExtUtils/
+xsubpp -typemap /opt/lib/perl5/5.14.2/ExtUtils/typemap
-typemap typemap GD.xs > GD.xsc && mv GD.xsc GD.c
gcc -c -I/opt/include -Wformat=0 -g -DVERSION=\"2.46\" -DXS_VERSION
+=\"2.46\" -fPIC
"-I/opt/lib/perl5/5.14.2/armv5tel-linux-thread-multi/CORE" -DHAVE_JPE
+G -DHAVE_FT -DHAVE_GIF -DHAVE_PNG -DHAVE_ANIMGIF
-DVERSION_33 -DHAVE_UNCLOSEDPOLY -DHAVE_FONTCONFIG -DHAVE_FTCIRCLE GD.
+c
Running Mkbootstrap for GD ()
chmod 644 GD.bs
rm -f blib/arch/auto/GD/GD.so
LD_RUN_PATH="/opt/lib" gcc -shared -g -L/usr/local/lib -fstack-protec
+tor GD.o -o blib/arch/auto/GD/GD.so \
-L/opt/lib -L/opt/lib -L/opt/lib -ljpeg -lfontconfig -lfreetype -lp
+ng12 -lz -lm -lgd \
chmod 755 blib/arch/auto/GD/GD.so
cp GD.bs blib/arch/auto/GD/GD.bs
chmod 644 blib/arch/auto/GD/GD.bs
/share/MD0_DATA/.qpkg/Optware/bin/perl "-Iblib/arch" "-Iblib/lib" bdf_
+scripts/bdf2gdfont.PLS bdf_scripts/bdf2gdfont.pl
Extracting bdf2gdfont.pl (with variable substitutions)
cp bdf_scripts/bdf2gdfont.pl blib/script/bdf2gdfont.pl
/share/MD0_DATA/.qpkg/Optware/bin/perl -MExtUtils::MY -e 'MY->fixin(sh
+ift)' -- blib/script/bdf2gdfont.pl
then 'make test' fails:
[/share/MD0_DATA/.cpan/build_dir/GD-2.46-hg6AiN] # make test
PERL_DL_NONLAZY=1 /share/MD0_DATA/.qpkg/Optware/bin/perl "-MExtUtils::
+Command::MM" "-e" "test_harness(0, 'blib/lib',
'blib/arch')" t/*.t
t/GD.t ........ Testing using png support.
t/GD.t ........ Failed 11/12 subtests
t/Polyline.t .. ok
Test Summary Report
-------------------
t/GD.t (Wstat: 11 Tests: 1 Failed: 0)
Non-zero wait status: 11
Parse errors: Bad plan. You planned 12 tests but ran 1.
Files=2, Tests=2, 2 wallclock secs ( 0.24 usr 0.01 sys + 1.00 cusr
+ 0.08 csys = 1.33 CPU)
Result: FAIL
Failed 1/2 test programs. 0/2 subtests failed.
make: *** [test_dynamic] Error 255
any help please?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.