Alan W. Irwin wrote: > On 2007-05-30 17:21+0900 Valery Pipin wrote: > > Having this and with option -DUSE_RPATH=OFF the building was smoothly > > ended with no errors. > > To test that all is well with the trailing colon business for rpath, > -DUSE_RPATH=ON (or no option since this is the default) should be used. (I > think that will probably be OK since you now have a correct > LD_LIBRARY_PATH, but it would be nice to know for sure.) Yes this works now with RPATH=ON as well. > > There were still some warning like > > > > verify-elf: WARNING: ./usr/lib/libplplotf77d.so.9.1.1: undefined > > symbol: for_iargc verify-elf: > > WARNING: ./usr/lib/libplplotf77d.so.9.1.1: undefined symbol: > > for_write_seq_fmt verify-elf: > > WARNING: ./usr/lib/libplplotf77d.so.9.1.1: undefined symbol: for_getarg > > verify-elf: WARNING: ./usr/lib/libplplotf77d.so.9.1.1: undefined > > symbol: for_cpystr verify-elf: > > WARNING: ./usr/lib/libplplotf95d.so.9.1.1: TEXTREL entry found: 0x0 > > IARGC and GETARG are important functions that should be defined (e.g., to > obtain Fortran command-line parsing). I just checked the Intel Fortran > Libraries Reference > (http://www.intel.com/software/products/compilers/techtopics/for_lib.htm), > and it appears at least those symbols will be defined if you use the > -Vaxlib option (as well as -O0). I have added -Vaxlib to FCFLAGS and it does not help. It may be because the intel libraries are not in standard path. As rpm complaine is
verify-elf: WARNING: ./usr/lib/libplplotf95d.so.9.1.1: not found: libimf.so verify-elf: WARNING: ./usr/lib/libplplotf95d.so.9.1.1: not found: libifport.so.5 verify-elf: WARNING: ./usr/lib/libplplotf95d.so.9.1.1: not found: libifcore.so.5 verify-elf: WARNING: ./usr/lib/libplplotf95d.so.9.1.1: undefined symbol: for_iargc Both libimf and libifort are in /usr/local/intel/lib that is in LD_LIBRARY_PATH. > BTW, Valery, I know you are keen on python/Numeric, and I am as well, but I > have looked recently at Fortran 95, and it is an excellent high-level > language for number crunching with many (or all?) of the Fortran 77 > irritations taken care of. Also, there is a large number of different > Fortran 95 compilers available including the Intel one and also gfortran > which is part of the Gnu Compiler Collection and free in both senses. > Anyhow, I see a pretty bright future for Fortran 95 so I am glad we have an > f95 interface to PLplot (thanks to Arjen's efforts last year). Our current > documentation for that interface is just a placeholder (where we took the > fortran 77 documentation and substituted 95 for 77 (!)) so those with an > interest in our f95 interface are urged to look at our f95 examples and not > pay too much attention to our formal f95 "documentation" until we update > it. Thanks for pointing this! Though, I prefer to draw results after computations. Also, there is a principal possibility to tight plplot and maxima via cl-plplot which was developed by Hazen Babcock. Though, the maxima folks are keen of gnuplot. kind regards, Valery ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Plplot-general mailing list Plplot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-general
