Re: [Plplot-devel] Install Plplot on Cygwin
(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, next one 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 I just want to use plplot from Fortran on Cygwin environment. I think that both two options doesn't include fortran environment. 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. Regards, Hiroyasu - 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
Re: [Plplot-devel] Install Plplot on Cygwin
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, next one 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 I just want to use plplot from Fortran on Cygwin environment. I think that both two options doesn't include fortran environment. 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. The problem with the second test is that libtool under Cygwin does not support dynamically loadable drivers. If you use the option ENABL_DYNDRIVERS=OFF then it should all work. I have been successful myself in using PLPlot within Fortran programs on this platform, though I only have the g77 and gfortran compilers. Your earlier problems seem to be due to the presence of Intel Fortran. Perhaps you could: - Install gfortran - Temporarily remove the path to Intel Fortran from your PATH environment variable (or simply rename the install directory so that CMake can not find that compiler) Regards, Arjen - 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
Re: [Plplot-devel] Install Plplot on Cygwin
Alan W. Irwin [EMAIL PROTECTED] writes: 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 Did my email make it to the list where I was able to replicate the error vis-a-vis Intel Fortran and cygwin? -jd - 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
Re: [Plplot-devel] Install Plplot on Cygwin
Alan W. Irwin [EMAIL PROTECTED] writes: On 2007-10-24 21:39-0400 Jim Dishaw wrote: Jim Dishaw [EMAIL PROTECTED] writes: Alan W. Irwin [EMAIL PROTECTED] writes: Jim, please correct me if you have a different experience, but my belief is the environment variable approach is going to set the fortran compiler and its options completely consistently so there should be no inconsistent extra options like /DIVF unless the build was done starting from a dirty build tree. [...]Jim, what happens if you try that simple case on Cygwin for 5.8.0-RC1? I downloaded the 5.8.0-RC1 source tarball and followed the build instructions on the Wiki for cygwin. First, I was not able to get things working without specifying -DBUILD_SHARED_LIBS=OFF. To Jim, Arjen, and Hiroyasu: Jim, I asked for a 5.8.0-RC1 test above, but since then I made a Cygwin fix in the svn version so I hope you (and also Arjen and Hirosyasu) will also do the two simple tests of the SVN version requested below. When I build with svn revision 7974 and have BUILD_SHARED_LIBS=ON and ENABLE_DYNDRIVERS=OFF I get the following error during make [ 0%] Building C object lib/csa/CMakeFiles/csirocsa.dir/csa.o /usr/bin/gcc.exe -Dcsirocsa_EXPORTS /Zl -DHAVE_CONFIG_H -DMAKINGCSADLL -o lib/csa/CMakeFiles/csirocsa.dir/csa.o -c /cygdrive/m/software/source/scientific/plplot-svn/lib/csa/csa.c gcc: /Zl: No such file or directory make[2]: *** [lib/csa/CMakeFiles/csirocsa.dir/csa.o] Error 1 make[2]: Leaving directory `/opt/build/cygwin-no-ivf' make[1]: *** [lib/csa/CMakeFiles/csirocsa.dir/all] Error 2 make[1]: Leaving directory `/opt/build/cygwin-no-ivf' make: *** [all] Error 2 The /Zl option is not appropriate with gcc. With the Microsoft C compiler, /Zl means omit default library information from the .obj, which, we should use when building with the Microsoft C compiler. Jim, what happens if you specify FC=ifort? Note, the FC environment variable method is documented on our wiki. We also give another non-FC alternative for specifying the fortran compiler, but that turns out not to be as reliable so we should remove that non-FC alternative from the wiki until the associated cmake bug that makes it unreliable gets fixed. The problem with the Intel compiler is that the Windows version expects that the forward slash denotes switches. The Makefiles generated by cmake in cygwin use the forward slash as path delimiters. I use the Windows Intel compiler in cygwin, but I have to make sure that I call it the correct way. Setting FC=ifort does not help the build. I am pretty sure we have tested the ifort compiler before on Cygwin using the FC approach with positive results, but if the path problem you have found previously with a non-FC approach persists for the FC approach, then please give a complete report, and we might be able to fix it or get help on the Cmake mailing list for the problem. I'm not sure what a full report is, but the only way I can see the Windows version of the Intel compiler working in cygwin is through the judicious use of the cygpath command. In my Makefile I have # Set variables based on the target architecture ifeq ($(ARCH),i686-pc-win32-ivf) # # Build environment for Intel Visual Fortran in win32 # # Path translation command for cygwin fullpath=$(shell cygpath -a -m $1) unixpath=$(shell cygpath -a -u $1) ...snip... # Implicit rules ifeq ($(DEBUG), 0) # For non-debug builds I want to generate the optimization report # /Qopt-report = Generate optimization report # /Qopt-report-file = Destination of the report %.o : %.f90 $(FC) /compile_only $(FCFLAGS) \ /Qopt-report /Qopt-report-file $*.rep \ $(call fullpath,$) /object:$@ else %.o : %.f90 $(FC) /compile_only $(FCFLAGS) $(call fullpath,$) /object:$@ endif %.o : %.c $(CC) /c $(CCFLAGS) $(call fullpath,$) /Fo$@ Those two tests are as follows (each should be done with an initially empty build tree, and I would appreciate a complete report (at least cmake command line, cmake.out, and make.out) for each. (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 $ cmake -DBUILD_SHARED_LIBS=ON -DENABLE_DYNDRIVERS=OFF -DCMAKE_VERBOSE_MAKEFILE=ON -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON /cygdrive/m/software/source/scientific/plplot-svn The output files are attached. I didn't bother to do the second test because the first one failed. cmake-1.out Description: Binary data make-1.out Description: Binary data Cheers -jd - 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
[Plplot-devel] Getting the Intel compilers to work on Cygwin
Hi Jim: I am separating out this separate topic using a descriptive subject line from the other topics your brought up in your e-mail. On 2007-10-25 19:53-0400 Jim Dishaw wrote: The problem with the Intel compiler is that the Windows version expects that the forward slash denotes switches. The Makefiles generated by cmake in cygwin use the forward slash as path delimiters. I use the Windows Intel compiler in cygwin, but I have to make sure that I call it the correct way. Setting FC=ifort does not help the build. I suspect the fix is pretty straightforward, but to make further progress with this on the CMake list, you will need to put together a simple complete CMake example to illustrate the problem. Such an example has already been prepared at http://cmake.org/HTML/Examples.html. All you need to add to it is the complete cmake.out results and make.out results when the CC environment variable points to the Intel C compiler. If you wrap the simple example and the cmake.out and make.out results into a tarball, I will forward it to the CMake list to see what they advise to resolve it. In CMake, compiler actions are controlled by configuration files in the Platform directory so the fix will probably be an added file in $prefix/share/cmake-2.4/Modules/Platform/ where $prefix is your CMake installation prefix. Once your simple example works with the Intel C compiler, then there is a method for adopting it instantly for PLplot (basically by distributing the added file in our own cmake/modules/Platform directory) until the fix gets distributed as part of CMake itself. Also, once we get the Intel C compiler configured properly for CMake on Cygwin, then generalizing the CMake fix to deal with the Intel Fortran (and C++ if that exists) compiler on Cygwin should be straightforward. But to get the ball rolling we need that complete simple example tarball from you first for the C case. 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
Re: [Plplot-devel] Install Plplot on Cygwin
Hi Jim, This post covers one final topic generated by your e-mail. On 2007-10-25 19:53-0400 Jim Dishaw wrote: $ cmake -DBUILD_SHARED_LIBS=ON -DENABLE_DYNDRIVERS=OFF -DCMAKE_VERBOSE_MAKEFILE=ON -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON /cygdrive/m/software/source/scientific/plplot-svn The output files are attached. I didn't bother to do the second test because the first one failed. Thanks for that complete report for revision 7974 of PLplot. It was good to see the complete results of the /Zl Intel compiler interference issue for this extremely simple case. So what happens with this simple test if you properly select your compiler using CC=gcc (or should that be CC=/usr/bin/gcc.exe ?) I predict the interference from the Intel compiler will be gone. If that proves to be correct, I don't need detailed results for that working simple case. Instead, please move on to the more interesting case of using all the above cmake parameters except for -DENABLE_DYNDRIVERS=ON In this case, both cmake.out and make.out will be different so I will need them both unless it works without problems. If it works without problems for revision 7974 of PLplot, then please move on to building and testing the installed examples. N.B. Your current cmake.out has the following warning: -- Looking for pkg-config - not found -- WARNING: Install-tree build will be disabled. Those messages mean you will have to first install the pkg-config Cygwin package which is available at http://www.cygwin.com/packages/ before you run cmake in order to get the installed examples to build. If Arjen and Hiroyasu encounter the same warning, I make the same suggestion to them to install the Cygwin version of pkg-config before they do anything else. 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
Re: [Plplot-devel] Using the GNU compilers without interference from the Intel compilers on Cygwin
Alan W. Irwin [EMAIL PROTECTED] writes: On 2007-10-25 19:53-0400 Jim Dishaw wrote: When I build with svn revision 7974 and have BUILD_SHARED_LIBS=ON and ENABLE_DYNDRIVERS=OFF I get the following error during make [ 0%] Building C object lib/csa/CMakeFiles/csirocsa.dir/csa.o /usr/bin/gcc.exe -Dcsirocsa_EXPORTS /Zl -DHAVE_CONFIG_H -DMAKINGCSADLL -o lib/csa/CMakeFiles/csirocsa.dir/csa.o -c /cygdrive/m/software/source/scientific/plplot-svn/lib/csa/csa.c gcc: /Zl: No such file or directory make[2]: *** [lib/csa/CMakeFiles/csirocsa.dir/csa.o] Error 1 make[2]: Leaving directory `/opt/build/cygwin-no-ivf' make[1]: *** [lib/csa/CMakeFiles/csirocsa.dir/all] Error 2 make[1]: Leaving directory `/opt/build/cygwin-no-ivf' make: *** [all] Error 2 The /Zl option is not appropriate with gcc. When multiple compilers are available, the only reliable way I know of to specify which one you want is with an environment variable. We have just been through that for the FC environment variable, but there are corresponding environment variables for the C compiler and C++ compiler you must set as well (see set environment variables to specify the compilers and compiler flags at http://www.miscdebris.net/plplot_wiki). So what happens when you set CC, CXX, and FC appropriately before the execution of cmake to obtain hopefully pure versions of gcc, g++, and g77 without interference from the corresponding Intel compilers? Actually, I did the above test with only the GNU compilers on the path. I removed the Intel Fortran compiler from the PATH variable. - 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
Re: [Plplot-devel] Install Plplot on Cygwin
Alan W. Irwin [EMAIL PROTECTED] writes: Hi Jim, This post covers one final topic generated by your e-mail. On 2007-10-25 19:53-0400 Jim Dishaw wrote: $ cmake -DBUILD_SHARED_LIBS=ON -DENABLE_DYNDRIVERS=OFF -DCMAKE_VERBOSE_MAKEFILE=ON -DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -DDEFAULT_NO_BINDINGS=ON /cygdrive/m/software/source/scientific/plplot-svn The output files are attached. I didn't bother to do the second test because the first one failed. So what happens with this simple test if you properly select your compiler using CC=gcc (or should that be CC=/usr/bin/gcc.exe ?) I did the test without Intel's or Microsoft's compilers in the path. The /Zl still remains. I did find the cause of it--it is my fault. I modified the UserOverride.cmake to add the /Zl in order to get the libraries to work correctly with the Microsoft compilers. My bad. The issue with Intel Fortran and Cygwin: - The Unix style path is being interpreted by the compiler as compiler switches, which causes the compiler to fail. The above issue reveals the following problem with cmake - When the Fortran compiler test fails when running cmake, the Fortran bindings should not be enabled. Currently, running cmake a second time will leave the Fortran bindings on. In the documentation we should state: If the build system has multiple compilers installed and visible in the executable search path, you must specify the compilers with the appropriate environment variables, e.g. FC and CC. When building with different compilers, always start with a clean build directory. -jd - 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
Re: [Plplot-devel] Getting the Intel compilers to work on Cygwin
Alan W. Irwin [EMAIL PROTECTED] writes: Hi Jim: I suspect the fix is pretty straightforward, but to make further progress with this on the CMake list, you will need to put together a simple complete CMake example to illustrate the problem. Such an example has already been prepared at http://cmake.org/HTML/Examples.html. All you need to add to it is the complete cmake.out results and make.out results when the CC environment variable points to the Intel C compiler. If you wrap the simple example and the cmake.out and make.out results into a tarball, I will forward it to the CMake list to see what they advise to resolve it. I have attached the cmake.out when I use the Microsoft C compiler with the example. It didn't get very far. cmake.out Description: Binary data Using - for compiler switches is not a problem. The -o needs to be a -Fo and the paths need to be converted from Unix style to Windows style via the cygpath command. - 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
Re: [Plplot-devel] Using the GNU compilers without interference from the Intel compilers on Cygwin
On 2007-10-26 00:00-0400 Jim Dishaw wrote: Actually, I did the above test with only the GNU compilers on the path. I removed the Intel Fortran compiler from the PATH variable. I am not sure of the internal workings of CMake on this, but it is entirely conceivable it is finding the Intel compiler some other way in addition to using the PATH. So I would not rely on setting the PATH variable to stop the interference. Instead, just set CC, CXX, and FC which as far as I know should bypass all additional searching for C, C++, and Fortran compilers and thus should (I predict) stop all interference between Intel and GNU compilers. This, of course, assumes you are making a build in an empty build tree and that you have a clean source tree (one where no builds have been done by accident before since once you do a source-tree build you cannot do a separate build tree build without unpacking a fresh source tarball or doing a fresh svn checkout of the source tree). Let me know whether my CC, CXX, and FC theory is correct. :-) 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
