On 2007-10-25 19:22+0900 Hiroyasu Yasuda wrote:

>> (1) The first test should have the following options:
>> 
>> -DBUILD_SHARED_LIBS=ON -DENABLE_DYNDRIVERS=OFF
>> -DCMAKE_VERBOSE_MAKEFILE=ON
>> -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON
>> 
>> 
>> (2) The second test should have the following options
>> 
>> -DBUILD_SHARED_LIBS=ON -DENABLE_DYNDRIVERS=ON
>> -DCMAKE_VERBOSE_MAKEFILE=ON
>> -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON
>
>
> Alan, I have already tested above two options. First one can be succeeded to 
> install.

Excellent.  This means that in general shared libraries will at least build on
Cygwin.  Please now build and test the
fully loaded PLplot case including fortran.  Use

export FC=g77

before running cmake to choose that fortran compiler (as documented in the
wiki).  Cmake ignores all fortran compilers other than the one you specify
with FC so if you have ifort installed as well, it will be completely
ignored if you choose FC=g77. From the Cygwin packages lists they do not yet
have the gfortran compiler packaged so gfortran is not a viable choice for
you at this time. Drop the last 3 options for case (1) above to get all
possible PLplot components including fortran.  Specify a value for the
installed prefix using the

-DCMAKE_INSTALL_PREFIX=/tmp/plplot/install

option.  (Replace /tmp/plplot/install above with wherever you want to
install PLplot with the "make install" command below)

run cmake in an empty build tree and save results to cmake.out.  Look at
those cmake.out results to be sure there are no errors and check especially
the summary at the end to make sure you have all desired PLplot
components.

Run make to build PLplot

make >& make.out

Look at those results to make sure there are no build errors.

Install the PLplot that has been built.

make install >& make_install.out

Check the make_install.out file for any problems.  You should note that
there is a long list of installed files that are installed in the
install tree with the prefix given above.  I assume just below that prefix
is /tmp/plplot/install, but it can be any (empty) directory that you choose
when you run cmake.

Build the installed examples.

cd /tmp/plplot/install/share/plplot5.8.0-RC1/examples/
make >& make_examples.out

(Note, the plplot5.8.0-RC1 directory will be the correct one to use both
for our 5.8.0-RC1 release and also for the latest svn trunk version, see
below.)

Look at make_examples.out to see if there were any errors in the examples
build. Note, the build should include some fortran 77 examples built with
g77 which should give you a good idea how to build your own fortran examples
with g77.

./plplplot-test.sh  --help

To see what possibilities there are for testing the installed and built
examples.  In general, you can do a default test by just running

./plplplot-test.sh >& plplot-test.out

Look at the postscript results of that test (in files like x01f.psc which is
produced with the first f77 example) with a postscript viewer to be sure all
is well.

N.B. In the above series of instructions for making a complete build of PLplot
on Cygwin and testing the results with some installed examples, I have
suggested you capture results at every stage in *.out files.  If there are
any troubles with any of the results, please send _all_ *.out files as part
of your complete error report.

> I just want to use plplot from Fortran on Cygwin environment.

Follow directions above, and you should be fine.

> I think that 
> both two options doesn't include fortran environment.

True, but simple tests like the above are important from our perspective to
debug any problems.  Thanks for helping us out this way.


> I would like to ask you 
> that can Plplot 5.7.4 or 5.8.0-RC1 call from fortran on Cygwin right now? If 
> you know that, please let me know the way to install.

This has been answered at least twice before, but I will try again. Avoid
all of the above for Cygwin.  Use latest svn trunk version (directions are
given at http://sourceforge.net/svn/?group_id=2915 for accessing it).  The
svn checkout of trunk gives you a similar (but improved) source tree to what
you get with 5.8.0-RC1.  You then specify that source tree when running
cmake, and the rest of the build should be the same sd what you have done
previously.  In a couple of weeks we plan to release 5.8.0 final with the
fixes that are currently in svn trunk.  At that point, you will probably
want to switch to the 5.8.0 tarball, but meanwhile use svn trunk to make
sure there are no additional cygwin problems for that case that we can fix
before 5.8.0 is released.

> next one (simple test 2) can not be succeeded with error message as follows 
> on 
> Cygwin.
>
> Could not open driver module ps
> libltdl error: No such file or directory
> make[2]: *** [drivers/ps.so] Error 1
> make[2]: Leaving directory `/home/yasu/plplot/b002'
> make[1]: *** [drivers/CMakeFiles/ps.dir/all] Error 2
> make[1]: Leaving directory `/home/yasu/plplot/b002'
> make: *** [all] Error 2

This is not the complete error report I requested.  Without that, I have no
idea whether a simple cmake adjustment will fix this issue (if it exists
for svn trunk) or not.

Also, since you still needed instructions about accessing the svn trunk
version above, it appears you did not do this test for that trunk version.
Errors like above are expected if you use any other version.

I cannot emphasize that enough.  For example, Arjen has recently speculated
that this case will not work.  That speculation may be correct, but it is
based on results for old versions of PLplot where such errors are expected
(since they didn't have my recent important Cygwin fix that is in svn
trunk).  Thus, we don't know the answer for sure until somebody with access
to the Cygwin platform steps forward and does the simple test 2 above with
complete error report for svn trunk.

Hiroyasu, I am hoping that you, Arjen, and Jim all do the requested test 2
for svn trunk with complete error report since if a problem exists it may
depend on what version of dynamic loading libraries each of you have
installed with Cygwin.  However, if instead you decide to concentrate on the
full PLplot test case with the -DENABLE_DYNDRIVERS=OFF workaround to pursue
your interest in using PLplot rather than helping us to debug it, that is
fine as well.  We like our users to be happy.  :-)

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to