On 2015-04-20 12:55-0700 Alan W. Irwin wrote: > Furthermore -debug works fine for me on MinGW/MSYS/Wine, but the only > extra output from it comes after the device is selected from the list > above. So to debug further you will have to (locally) add informative > pldebug calls to the code near where the error message above > "plInitDispatchTable: Could not open drivers directory, aborting > operation" is being generated. > > I look forward to seeing those results from you.
Hi Arjen: Actually, I take that "works fine for me" back. If you look at the code, the error message is generated after a call to plGetDrvDir which has pldebug() calls in it. Those work on Linux. Here is what happens on Linux when the the ps device has not been built (to cut down on the debug output). software@raven> examples/c/x00c -debug -dev psc -o test.psc plLoadDriver: Device not loaded! plLoadDriver: tag=psc, drvidx=0 plGetDrvDir: Using /home/software/plplot/HEAD/build_dir/drivers as the driver directory. plLoadDriver: Trying to load ps on /home/software/plplot/HEAD/build_dir/drivers/ps plLoadDriver: lt_dlopenext failed because of the following reason: file not found Unable to load driver: ps. *** PLPLOT ERROR, IMMEDIATE EXIT *** Unable to load driver Program aborted So there is a message from plGetDrvDir above on exactly what drivers directory is being used in the build tree (which gets the build-tree version of that directory because of the plInBuildTree() result). On MinGW/MSYS/Wine here is the equivalent result (again without the ps.dll device available to make output short). bash.exe-3.1$ examples/c/x00c -debug -dev psc -o test.psc plLoadDriver: Device not loaded! plLoadDriver: tag=psc, drvidx=0 plLoadDriver: Trying to load ps on ps plLoadDriver: lt_dlopenext failed because of the following reason: No error information Unable to load driver: ps. *** PLPLOT ERROR, IMMEDIATE EXIT *** Unable to load driver Program aborted So in my particular MinGW/MSYS/Wine case I get this very strange result that either (1) there is no call to plGetDrvDir at all or (2) somehow pldebug is not working for just that particular routine. So I now find myself in the position of having to debug the -debug option on this platform, and I hope you try that as well. And if you figure out that last sentence, it means you are truly a PLplot guru. :-) 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); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); 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 __________________________ ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
