Hi Alan,
On 2009-03-30 19:44, Alan W. Irwin wrote: > > It's a long shot, but there was some purpose to my question. So please > answer it with the _exact_ command (test-drv-info + argument), that was run > by make VERBOSE=1 including the directory the command was run in. > > test-drv-info is simply a renamed version of get-drv-info with no actual > code changes. So it bothers me that there is absolutely no error message > from it. (There have always been such error messages in the past if > something was wrong with the dynamic loading or with the argument that was > used.) What happens if you use a different/wrong argument to it? Do you > get > an error message then, and if so what? > Well, I solved the problem: it turns out that Werner was on the right track - I needed to expand the PATH environment variable, not with the drivers subdirectory that contains the DLLs, but with the src subdirectory, as apparently "test-drv-info" links to "libplplot-9.6.1.dll"! I realised that something like this was going wrong by manually running it with various arguments and extra print-statements. (By the way: it is using libtool as supplied by Cygwin. Interestingly when I forced it to use Werner's utilities, it did run! So, in that case it does not seem to depend on libplplot-9.6.1.dll ...) > I made some minor CMake changes to the way the code is built and run so > probably the best bet is there is something wrong there for the Cygwin case > (but not for the actual C-code itself). > >>> >>> If our build system chooses libltdl, do you have the latest/greatest >>> version >>> installed properly? >>> >> >> Quite probably it is an old one, but as I said before: it has worked in >> a previous build. So my suspicion is that the relatively new >> test-drv-info program does something different. I will try and find >> out what that difference is. > > I have just double-checked by downloading get-drv-info.c (revision 9475) > from our repository and it is identical to test-drv-info.c. So the > issue is > not due to a code change between get-drv-info.c and test-drv-info.c. > No, it is indeed the PATH that requires attention. That brings me to the following question: is it possible to expand the PATH variable automatically during the build process? I can of course expand it before I start "make", but then we burden every user with that. Putting that into the Makefiles seems much more elegant. Or at the very least: that is what I think now. Regards, Arjen Delft Hydraulics, GeoDelft, the Subsurface and Groundwater unit of TNO and parts of Rijkswaterstaat have joined forces in a new independent institute for delta technology, Deltares. Deltares combines knowledge and experience in the field of water, soil and the subsurface. We provide innovative solutions to make living in deltas, coastal areas and river basins safe, clean and sustainable. DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
