[Plplot-devel] Build of 5.6.1 RC1 on Slackware 10.2 with Intel fortran

[Bryan P. <pet...@ma...>]

OS:  Slackware 10.2
gcc version:  3.3.6
Intel ifort version:  9.0 20051020 (this is 9.0.028)

defined FC=ifort, F77=ifort, F95=ifort

Configure results:

host:		i686-pc-linux-gnu
have_x:		yes
prefix:		/usr/local/plplot
CC CFLAGS:	gcc -g -O2 -mieee-fp
CXX CXXFLAGS:	g++ -g -O2 -mieee-fp
F77 FFLAGS:	ifort -g
FC FCFLAGS:	ifort -g
LIB_TAG: 
devices:	 png jpeg lj_hpgl null pbm plmeta ps pstex xterm tk xfig xwin

Available device drivers:
static: 
dynamic:	gd.la hpgl.la null.la pbm.la plmeta.la ps.la pstex.la tek.la tk.la xfig.la xwin.la

Compilation options:
with_debug:	no

Library options:
enable_shared:	yes		enable_static:	yes
with_rpath:	yes		with_double:	no

Optional libraries:
with_qhull:	yes		with_csa:	yes
with_freetype:	yes		with_pthreads:	yes

Language Bindings:
enable_f77:	yes		enable_f95:	yes
enable_cxx:	yes		enable_java:	yes
enable_python:	yes		enable_octave:	yes
enable_tcl:	yes		enable_itcl:	no
enable_pdl:	no

-------------

Results of build:

1. Driver tek.c failed to compile due to unterminated #if and #ifdef
statements.  Problem appears to be solved by correcting the blocks

#if defined(PLD_xterm)
   "xterm:Xterm Window:1:tek:18:xterm"
#ifdef

(one for each of the driver components in the tek.c file) to

#if defined (PLD_xterm)
   "xterm:Xterm Window:1:tek:18:xterm"
#endif

2. Example x12f.f90 failed with the error

ifort -I../../include  -I../../bindings/f95 -g -c -o x12f.o x12f.f90
fortcom: Error: x12f.f90, line 58: The type of the actual argument differs
from the type of the dummy argument.   [DBLE]
         call plptex( dble (1980._plflt+i+0.5_plflt), y0(i+1)+1._plflt, &
---------------------^
fortcom: Error: x12f.f90, line 62: The type of the actual argument differs
from the type of the dummy argument.   [DBLE]
         call plmtex( 'b', 1._plflt, dble ((i+1)*0.1_plflt-0.05_plflt), &
------------------------------------^
compilation aborted for x12f.f90 (code 1)

You will note that I built the library for single precision.  The remaining
fortran 95 examples built and ran properly.  I also ran all the c and 
fortran 77 examples and they appear to work properly (with the exception 
of the unicode examples - see #3 below).

3. I haven't been able to get the psttf driver to build properly yet.  I
installed LASi-1.0.4 but when I try to build I get the error:

  g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../include
-I/usr/local/includei -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/X11R6/include -I/usr/include/freetype2 -g
-O2 -mieee-fp -MT psttf_la-psttf.lo -MD -MP -MF .deps/psttf_la-psttf.Tpo -c
psttf.cc  -fPIC -DPIC -o .libs/psttf_la-psttf.o
psttf.cc: In function `void plD_tidy_psttf(PLStream*)':
psttf.cc:604: error: no matching function for call to `LASi::PostscriptDocument
    ::write(std::ostream&, int&, int&, int&, int&)'
/usr/local/include/LASi.h:125: error: candidates are: void
    LASi::PostscriptDocument::write(std::ostream&)
psttf.cc:609: error: no matching function for call to `LASi::PostscriptDocument
    ::write(std::ofstream&, int&, int&, int&, int&)'
/usr/local/include/LASi.h:125: error: candidates are: void
    LASi::PostscriptDocument::write(std::ostream&)

I have very little experience with C++ so I don't see an immediate fix for
this one although I will keep trying.

Bryan Peterson
bry...@by...