On 2009-04-24 14:36-0500 Geoffrey Furnish wrote: > Werner Smekal writes: > > make VERBOSE=1 > > I found a cmake var for this too. > > > > Well, I go to the installed examples dir, and run xtk01 under gdb, and it > > > tells me there is no debugging info available. > > > > > I usually debug in the build tree. Add the "-DBUILD_TEST=ON" to the > > cmake options and all examples will be compiled in the built tree. > > When I do this, I get a build failure in a Fortran example. I'm focused on > something else, and haven't written Fortran in nearly 15 years.
When running into a component problem like this where you are not interested in the component (and also for speed) just disable the componenent, e.g., -DENABLE_f95=OFF > So I'll > include my comake invocation script, my cmake output, and my build log. And > maybe someone invovled with the Fortran examples can debug it? This was on > Fedora 8. Thanks for that fortran 95 error report. However, I don't think we should change anything in PLplot to deal with this issue. The exit statements in examples/f95/x20f.f90 are causing the trouble for your f95 compiler. Those are very different from "call exit". The bare exit command is used to escape loops in Fortran 95. Modern gfortran implements it as does the Intel compiler (and presumably all other commercial Fortran compilers). Apparently, you have some old version of gfortran that doesn't have bare exit implemented yet. Our Fortran 95 examples build and work great here with gfortran (GNU Fortran (Debian 4.3.2-1.1) 4.3.2). I am now going to rant just a little about one of my pet peeves, the so-called enterprise editions of Linux distributions. Those distributions are filled with out-dated software which I think you are the victim of in this case since you have mentioned RHEL version 4 in other contexts. I think the source of the trouble is corporate IT departments which have been conditioned to demand non-changing software by proprietary software vendors. They have made similar demands of Linux distribution vendors, and as a result the enterprise edition of Linux was born. But the whole idea should have been aborted instead since it is fundamentally not consistent with the pace of development for Linux. Linux is not and never will be a toaster. I assume every 3 years or so these corporate IT departments are forced to change their enterprise Linux version. There must be huge training costs associated with such enormous change attempted all at once. There has got to be a better way of having a steady diet of reliable, well-tested change that keeps up with Linux development for just the key libraries and apps that a particular corporation wants. The idea would be to give corporation workers the chance to adjust to the steady change associated with Linux without having huge training costs associated with large abrupt changes. You also avoid the hidden costs of old Linux software that sometimes (as above) just doesn't cut it. End rant. 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 __________________________ ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
