BTW, I have others warnings like Verifying ELF objects in /home/vv/tmp/plplot-buildroot (arch=normal,fhs=normal,rpath=normal,stack=normal,textrel=relaxed,unresolved=relaxed) verify-elf: WARNING: ./usr/lib/libcsirocsa.so.0.0.1: undefined symbol: sqrt verify-elf: WARNING: ./usr/lib/libcsirocsa.so.0.0.1: undefined symbol: floor verify-elf: WARNING: ./usr/lib/libcsirocsa.so.0.0.1: undefined symbol: ceil verify-elf: WARNING: ./usr/lib/libcsirocsa.so.0.0.1: undefined symbol: hypot
Does it mean that libcsirocsa is compiled without -lm ? > > I am sure you knew this, but just to keep the record straight it should > > be FC, i.e., > > > > export FC='ifort -O0 -Vaxlib' > > > > not FCFLAGS. > > I'm sorry the previous message was misleading. I have used > export FC='ifort -O0 -Vaxlib' exactly. During the build I observed that > cmake understood it. > > > > 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. > > > > I think you are correct that rpm won't work for your setup since rpm > > expects everything is installed in standard locations. > > > > At this point, you may just want to turn off the f77 and f95 interfaces > > since you are not primarily interested in those. > > I thought this interface should work on my mashine unless the warnings. > > > However, in case you have > > some remaining interest or someone else runs into ifort problems there is > > still the alternative of doing a simple PLplot build and install without > > worrying about the special requirements of rpm. That is, use the normal > > cmake; make; and make install. I think that procedure would work > > correctly on any system where ifort is installed in a non-standard > > location. After all, ifort knows how to link everything (i.e., it knows > > the locations of its libraries), and at run-time, your LD_LIBRARY_PATH > > tells the run-time loader where to find those same fortran libraries. > > > > A comprehensive test of the fortran interface to PLplot built and > > installed that way is provided if you try "make install", and then run > > the standard installed examples test (e.g., run "make" and > > "./plplot-test.sh" in $PREFIX/share/plplot5.7.3/examples, where $PREFIX > > is the PLplot > > installation prefix you specified to the cmake command with the > > -DCMAKE_INSTALL_PREFIX option.) You could also try "ldd -r > > $PREFIX/lib/libplplotf95d.so" to make sure all libraries are found and > > those libraries define all required symbols. > > This is worth to try. > > 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 ------------------------------------------------------------------------- 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
