From: <hba...@ma...> - 2006-05-21 18:01:04
|
Hello, Release candidate #1 for PLplot 5.6.1 is now available for download at: http://sourceforge.net/project/showfiles.php?group_id=2915 This is a *test* release for the final version of PLplot 5.6.1. If you have the time & the inclination, please download it and let us know if does/does not work on your system of choice. best, -Hazen |
From: steven m. <ste...@es...> - 2006-05-21 19:11:39
|
hba...@ma... [2006-05-21, 14:00:22]: > > Hello, > > Release candidate #1 for PLplot 5.6.1 is now available for download at: > > http://sourceforge.net/project/showfiles.php?group_id=2915 > > This is a *test* release for the final version of PLplot 5.6.1. If > you have the time & the inclination, please download it and let us > know if does/does not work on your system of choice. even if f95 is disabled, the installation still creates the directory $(libdir)/fortran/modules/plplot steven Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm |
From: Alan W. I. <ir...@be...> - 2006-05-21 19:59:37
|
On 2006-05-21 14:00-0400 hba...@ma... wrote: > > Hello, > > Release candidate #1 for PLplot 5.6.1 is now available for download at: > > http://sourceforge.net/project/showfiles.php?group_id=2915 > > This is a *test* release for the final version of PLplot 5.6.1. If you have > the time & the inclination, please download it and let us know if does/does > not work on your system of choice. Thanks, Hazen. Your new release candidate tarball, plplot-5.6.1_RC1.tar.gz, works for me. I will describe some details for the benefit of PLplot users that want to give this a try. My Ubuntu Breezy system has been loaded up with all the development packages (e.g., Tcl, free java, octave, gfortran) required to take advantage of virtually all language interfaces and device drivers of PLplot that are accessible from Linux. The build and install was accomplished as follows: ./configure --prefix=$PREFIX --disable-static --enable-f95 F77=f95 \ --with-prebuiltdoc >& configure.out make >& make.out make install >& make_install.out PREFIX is my chosen install prefix (/usr/local/plplot in my case). If you --enable-f95, F77 must be set to whatever is appropriate for your fortran 95 compiler which was f95 in my particular case. Although not necessary in my case, you might also have to set FFLAGS to to whatever is appropriate for FCFLAGS. These --enable-f95 workarounds should not be necessary when we can base our release on libtool-2.0 (scheduled for release later this year). The --with-prebuiltdoc option allows me to browse the new documentation (including the initial cut at some fortran 95 documentation) at $PREFIX/share/doc/plplot/html/index.html. After the build and install I did the usual test of compiling the installed examples and testing them: cp -a $prefix/share/plplot5.6.1_RC1/examples/ /tmp/examples cd /tmp/examples make ./plplot-test.sh script Spot checks of the resulting 162 (!) postscript files looked good, and a comprehensive check showed these postscript results were identical with previous ones. So 5.6.1 release candidate 1 is looking good on Ubuntu Breezy, and I strongly encourage RC1 reports from our users (going through all the steps above) to make sure 5.6.1 gets comprehensively tested on as wide a variety of platforms as possible before it is released in final form. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Orion P. <or...@co...> - 2006-05-22 17:39:38
|
Alan W. Irwin wrote: > > PREFIX is my chosen install prefix (/usr/local/plplot in my case). If you > --enable-f95, F77 must be set to whatever is appropriate for your > fortran 95 > compiler which was f95 in my particular case. Compiling on Fedora Core Development I do not appear to need to specify F77=f95. What problems did you see when you omitted it? I don't see the extra "yes" after the "accepts -g" check, and no obvious errors. > > After the build and install I did the usual test of compiling the installed > examples and testing them: > > cp -a $prefix/share/plplot5.6.1_RC1/examples/ /tmp/examples > cd /tmp/examples > make > ./plplot-test.sh script > > Spot checks of the resulting 162 (!) postscript files looked good, and a > comprehensive check showed these postscript results were identical with > previous ones. Most of them look good, except: Testing front-end python Traceback (most recent call last): File "/builddir/build/BUILD/plplot-5.6.1_RC1/test/../examples/python/x03", line 36, in ? import xw03 File "/builddir/build/BUILD/plplot-5.6.1_RC1/examples/python/xw03.py", line 63, in ? main() File "/builddir/build/BUILD/plplot-5.6.1_RC1/examples/python/xw03.py", line 21, in main i.shape = (-1,1) ValueError: can only specify one unknown dimension Seen in xw03.py, 08, 09, 11, 15, 16, 18, 22 Also, I still got: PASS: plplot-test.sh ================== All 1 tests passed ================== even with the above errors. Finally, I guess I should have weighed in earlier on the debate about where to put the fortran .mod files earlier, but I'm not sure I'm happy about /usr/lib/fortran/modules/plplot. Why so many subdirs? Why not just /usr/lib/plplot? The former makes for more work for distribution makers (who owns /usr/lib/fortran?). Otherwise, everything looks great. Good work everyone. -- Orion Poplawski System Administrator 303-415-9701 x222 Colorado Research Associates/NWRA FAX: 303-415-9702 3380 Mitchell Lane, Boulder CO 80301 http://www.co-ra.com |
From: Alan W. I. <ir...@be...> - 2006-05-22 19:11:13
|
Thanks, Orion, for your report. Comments in context below....Alan On 2006-05-22 11:39-0600 Orion Poplawski wrote: > Alan W. Irwin wrote: >> >> PREFIX is my chosen install prefix (/usr/local/plplot in my case). If you >> --enable-f95, F77 must be set to whatever is appropriate for your fortran >> 95 >> compiler which was f95 in my particular case. > > Compiling on Fedora Core Development I do not appear to need to specify > F77=f95. What problems did you see when you omitted it? I don't see the > extra "yes" after the "accepts -g" check, and no obvious errors. Generally, we have found you must specify F77=f95 (or whatever is appropriate for your fortran 95 compiler) if there is a fortran 77 compiler installed. The explanation I got on the libtool list was fortran 77 compilers tended to mess up the fortran 95 settings so setting F77 cuts the fortran 77 compiler completely out of the loop to get around this. So we have just gotten in the habit of setting F77. But that proved necessary on most platforms for a slightly different version of our fortran configuration that has been changed since so it is possible this problem has been fixed and setting F77 is no longer required. Since Orion's platform did not need the F77 setting, I ask anybody else who tests this to let me know whether setting F77 is absolutely necessary anymore on any platform. If this workaround were no longer necessary on any platform, that would be excellent news. > >> >> After the build and install I did the usual test of compiling the >> installed >> examples and testing them: >> >> cp -a $prefix/share/plplot5.6.1_RC1/examples/ /tmp/examples >> cd /tmp/examples >> make >> ./plplot-test.sh script >> >> Spot checks of the resulting 162 (!) postscript files looked good, and a >> comprehensive check showed these postscript results were identical with >> previous ones. > > Most of them look good, except: > > Testing front-end python > Traceback (most recent call last): > File "/builddir/build/BUILD/plplot-5.6.1_RC1/test/../examples/python/x03", > line 36, in > ? > import xw03 > File "/builddir/build/BUILD/plplot-5.6.1_RC1/examples/python/xw03.py", line > 63, in ? > main() > File "/builddir/build/BUILD/plplot-5.6.1_RC1/examples/python/xw03.py", line > 21, in main > i.shape = (-1,1) > ValueError: can only specify one unknown dimension > > Seen in xw03.py, 08, 09, 11, 15, 16, 18, 22 You are the first to report this problem. The python examples certainly work on my two systems (Ubuntu Breezy with Python 2.4.2/Numeric-23.8 and Debian stable with Python 2.3.5/Numeric-23.8). What is your version of Python _and_ Numeric? Fedora is notoriously cutting edge so is it possible you are using one of the Numeric successors such as Numarray or NumPy? The NumPy project advertises themselves (see http://numeric.scipy.org/#older_array) as the ultimate successor to Numeric and Numarray, but I don't know how much they have convinced others of this. At some point I may move us to NumPy, but I really haven't had time to investigate whether NumPy has good distribution support. For now, I know Numeric does have that support (with the possible exception of Fedora), so that is why I am sticking with Numeric for now. > > Also, I still got: > > PASS: plplot-test.sh > ================== > All 1 tests passed > ================== > > even with the above errors. That is not right. However, I don't maintain the complicated make check logic myself (the installed examples test I advocate above has much simpler logic behind it) so somebody else will have to do the fix. > > > Finally, I guess I should have weighed in earlier on the debate about where > to put the fortran .mod files earlier, but I'm not sure I'm happy about > /usr/lib/fortran/modules/plplot. Why so many subdirs? Why not just > /usr/lib/plplot? The former makes for more work for distribution makers (who > owns /usr/lib/fortran?). At this point, I don't think the Linux community has really come to grips with this fortran 95 install location issue since it is only recently that libre fortran 95 compilers (gfortran and g95) became viable solutions. The fortran part of the above install location was recommended in a generic way by someone on the Linux File Hierarchy Standards list, but that is certainly not an official decision and they may change their minds later. The modules part of it was my invention to be more informative, but if that turns out to be a major problem we can certainly move to /usr/lib/fortran/plplot in the future or anything else that finally becomes officially recommended by the LFHS group. For now, though, I think we should just stick with what we have. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Orion P. <or...@co...> - 2006-05-22 19:44:17
|
Alan W. Irwin wrote: > Thanks, Orion, for your report. Comments in context below....Alan > > Generally, we have found you must specify F77=f95 (or whatever is > appropriate for your fortran 95 compiler) if there is a fortran 77 compiler > installed. Okay, that's the case here. f77 is not installed. > > You are the first to report this problem. The python examples certainly > work on my two systems (Ubuntu Breezy with Python 2.4.2/Numeric-23.8 and > Debian stable with Python 2.3.5/Numeric-23.8). What is your version of > Python _and_ Numeric? Indeed, I don't see the problem on Fedora 5. Devel has python 2.4.3 and Numeric 23.7. 5 has python 2.4.2 and Numeric 23.7. I'll poke around some more. -- Orion Poplawski System Administrator 303-415-9701 x222 Colorado Research Associates/NWRA FAX: 303-415-9702 3380 Mitchell Lane, Boulder CO 80301 http://www.co-ra.com |
From: Orion P. <or...@co...> - 2006-05-24 17:39:32
|
Orion Poplawski wrote: > Alan W. Irwin wrote: >> >> You are the first to report this problem. The python examples certainly >> work on my two systems (Ubuntu Breezy with Python 2.4.2/Numeric-23.8 and >> Debian stable with Python 2.3.5/Numeric-23.8). What is your version of >> Python _and_ Numeric? > > Indeed, I don't see the problem on Fedora 5. Devel has python 2.4.3 and > Numeric 23.7. 5 has python 2.4.2 and Numeric 23.7. I'll poke around > some more. > Confirmed as an issue with Numeric 23.7 and python 2.4.3. Updating to 24.2 fixes so I've filed a bug with Fedora to try to get it updated. Any plans to move to numpy? -- Orion Poplawski System Administrator 303-415-9701 x222 Colorado Research Associates/NWRA FAX: 303-415-9702 3380 Mitchell Lane, Boulder CO 80301 http://www.co-ra.com |
From: Geoffrey F. <fu...@li...> - 2006-05-22 21:57:48
|
Alan W. Irwin writes: > Orion Poplawski wrote: > > Finally, I guess I should have weighed in earlier on the debate about > > where to put the fortran .mod files earlier, but I'm not sure I'm happy > > about /usr/lib/fortran/modules/plplot. Why so many subdirs? Why not > > just /usr/lib/plplot? The former makes for more work for distribution > > makers (who owns /usr/lib/fortran?). > > At this point, I don't think the Linux community has really come to grips > with this fortran 95 install location issue since it is only recently that > libre fortran 95 compilers (gfortran and g95) became viable solutions. The > fortran part of the above install location was recommended in a generic > way by someone on the Linux File Hierarchy Standards list, but that is > certainly not an official decision and they may change their minds > later. The modules part of it was my invention to be more informative, but > if that turns out to be a major problem we can certainly move to > /usr/lib/fortran/plplot in the future or anything else that finally > becomes officially recommended by the LFHS group. For now, though, I > think we should just stick with what we have. ??? Maybe I put my foot in the wrong place on that. I thought I had registered support for putting the Fortran modules under the $prefix. |
From: Alan W. I. <ir...@be...> - 2006-05-21 21:18:40
|
On 2006-05-21 21:11+0200 steven mestdagh wrote: > hba...@ma... [2006-05-21, 14:00:22]: >> >> Hello, >> >> Release candidate #1 for PLplot 5.6.1 is now available for download at: >> >> http://sourceforge.net/project/showfiles.php?group_id=2915 >> >> This is a *test* release for the final version of PLplot 5.6.1. If >> you have the time & the inclination, please download it and let us >> know if does/does not work on your system of choice. > > even if f95 is disabled, the installation still creates the directory > $(libdir)/fortran/modules/plplot Thanks, Steven, for spotting that. Fixed in cvs (and therefore in the final release). 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: steven m. <ste...@es...> - 2006-05-21 22:07:00
|
hba...@ma... [2006-05-21, 14:00:22]: > > Hello, > > Release candidate #1 for PLplot 5.6.1 is now available for download at: > > http://sourceforge.net/project/showfiles.php?group_id=2915 > > This is a *test* release for the final version of PLplot 5.6.1. If > you have the time & the inclination, please download it and let us > know if does/does not work on your system of choice. With 5.6.0, I had some problems with the pstex driver. I get a SIGSEGV (on OpenBSD), which can be prevented by the following patch. However, the resulting .eps_t file does not contain any label text. So maybe there is a better fix? steven --- drivers/pstex.c.orig Mon Jan 19 20:10:19 2004 +++ drivers/pstex.c Mon Apr 17 01:34:40 2006 @@ -260,6 +261,11 @@ parse_str(const char *str, char *dest) "psi", "Psi", "omega", "Omega"}; plgesc(&esc); + + if (str == NULL) { + *tp = '\0'; + return; + } while (*str) { Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm |
From: Arjen M. <arj...@wl...> - 2006-05-22 07:39:54
|
hba...@ma... wrote: > > Hello, > > Release candidate #1 for PLplot 5.6.1 is now available for download at: > > http://sourceforge.net/project/showfiles.php?group_id=2915 > > This is a *test* release for the final version of PLplot 5.6.1. If > you have the time & the inclination, please download it and let us > know if does/does not work on your system of choice. Yesterday, working in my development tree, I found two problems on Cygwin and one on Windows: Cygwin: 1. There is a problem with gfortran and shared libraries: I have to disable shared libraries to get the examples to build properly. I have reported the bug (you get messages about duplicate gfortran symbols during the link phase). But disabling the shared libraries makes the error go away. Unfortunate, but at least there is a workaround. 2. The auxiliary program plflt does not get built properly. I have stared at the generated makefile, but the rule to make plflt$(EXEEXT) from $plflt_OBJECTS is _not_ followed (all looks okay to me, but the program is being built directly). The very ugly workaround is: % make % gcc -o plflt plft.c -I../../include % ./plflt % make Can anyone have a look at this? (I added a line to define plflt_CFLAGS in Makefile.am but this did not solve the issue - of course it wouldn't: make takes a default rule rather than the rule it should take) Windows: 3. The DLL version does not compile at the moment - changes in the API (plrgbhls, ...) that are not reflected in the stubs for the DLL version. The static version works splendidly. I do not know when I will have time to solve issue 3 - maybe tomorrow. Issue 2 is really puzzling Issue 1 is out of our control. Regards, Arjen |
From: Alan W. I. <ir...@be...> - 2006-05-22 23:01:49
|
On 2006-05-22 16:57-0500 Geoffrey Furnish wrote: > Alan W. Irwin writes: > > Orion Poplawski wrote: > > > Finally, I guess I should have weighed in earlier on the debate about > > > where to put the fortran .mod files earlier, but I'm not sure I'm happy > > > about /usr/lib/fortran/modules/plplot. Why so many subdirs? Why not > > > just /usr/lib/plplot? The former makes for more work for distribution > > > makers (who owns /usr/lib/fortran?). > > > > At this point, I don't think the Linux community has really come to grips > > with this fortran 95 install location issue since it is only recently that > > libre fortran 95 compilers (gfortran and g95) became viable solutions. The > > fortran part of the above install location was recommended in a generic > > way by someone on the Linux File Hierarchy Standards list, but that is > > certainly not an official decision and they may change their minds > > later. The modules part of it was my invention to be more informative, but > > if that turns out to be a major problem we can certainly move to > > /usr/lib/fortran/plplot in the future or anything else that finally > > becomes officially recommended by the LFHS group. For now, though, I > > think we should just stick with what we have. > > ??? Maybe I put my foot in the wrong place on that. I thought I had > registered support for putting the Fortran modules under the $prefix. Correction: By default it goes under $prefix/lib/fortran/modules/plplot (which translates to what Orion and I said above for prefix = /usr). So you have full control of the prefix with the --prefix configure option. However, there are a lot more possibilities then this prefix default which you can check out by looking at the libdir (and other *dir) documentation using ./configure --help. I have checked that --libdir actually works for PLplot. As I said when I commented on that good result before, Geoffrey, your disambiguation problems are probably over if you use some of those *dir configure options. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Koen v. d. D. <kvd...@ea...> - 2006-05-22 23:37:24
|
On May 21, 2006, at 2:00 PM, hba...@ma... wrote: > > This is a *test* release for the final version of PLplot 5.6.1. If > you have the time & the inclination, please download it and let us > know if does/does not work on your system of choice. Builds fine on OS X using fink (ppc, 10.4 tree): host: powerpc-apple-darwin have_x: yes prefix: /sw CC CFLAGS: gcc -Wno-long-double CXX CXXFLAGS: g++ -g -O2 F77 FFLAGS: gfortran -g -O2 FC FCFLAGS: gfortran -g -O2 LIB_TAG: d devices: aqt png jpeg gif hp7470 hp7580 lj_hpgl mem null pbm plmeta ps pstex tk xfig xwin Available device drivers: static: dynamic: aqt.la gd.la hpgl.la mem.la null.la pbm.la plmeta.la ps.la pstex.la tk.la xfig.la xwin.la Compilation options: with_debug: no Library options: enable_shared: yes enable_static: yes with_rpath: no with_double: yes Optional libraries: with_qhull: yes with_csa: yes with_freetype: yes with_pthreads: no Language Bindings: enable_f77: yes enable_f95: yes enable_cxx: yes enable_java: yes enable_python: yes enable_octave: yes enable_tcl: yes enable_itcl: no enable_pdl: no Also no problems with the examples. - Koen. |
From: Alan W. I. <ir...@be...> - 2006-05-23 22:56:25
|
On 2006-05-22 00:06+0200 steven mestdagh wrote: > With 5.6.0, I had some problems with the pstex driver. > > I get a SIGSEGV (on OpenBSD), which can be prevented by the following > patch. However, the resulting .eps_t file does not contain any label text. > So maybe there is a better fix? > > steven > > --- drivers/pstex.c.orig Mon Jan 19 20:10:19 2004 > +++ drivers/pstex.c Mon Apr 17 01:34:40 2006 > @@ -260,6 +261,11 @@ parse_str(const char *str, char *dest) > "psi", "Psi", "omega", "Omega"}; > > plgesc(&esc); > + > + if (str == NULL) { > + *tp = '\0'; > + return; > + } > > while (*str) { > I confirm segfaults on both Debian Stable and Ubuntu Breezy as well. So it appears some bit rot has set in. There was an overview of the purpose of the pstex device driver in 2001 list mail which indicated it was designed to short-circuit the process of using -dev xfig, importing the result to xfig, and exporting the result to latex. But I am not sure that short-circuit is of much utility any more since the only purpose of the short-circuit, as far as I know, was to get access to some Type 1 fonts. Other than a spattering of 2001 list mail (which is no longer available to anybody unless they saved it at the time), the pstex device driver is undocumented. Those nice-looking fonts did impress me in 2001, but we have long since had those completely supported in the ps device driver, and now we have introduced powerful new Complex Text Layout (CTL) and TrueType font capability with the psttf device driver. Also, it is completely straightforward to import either ps or psttf results into latex documents. Thus, I am largely convinced the pstex device is not worth supporting any more especially since nobody else has responded to this bug report or my off-list question to other PLplot core developers about this device. So unless someone surprises me in the next 24 hours and volunteers to support this device, I have decided to completely disable its build on Unix systems for 5.6.1 while keeping the pstex.c code still available in CVS and the distribution tarball. This change should allow anybody who is still keen on pstex to fix that code in the future while discouraging anybody from attempting to build it when we know it segfaults. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |
From: Alan W. I. <ir...@be...> - 2006-05-24 18:59:25
|
On 2006-05-24 11:39-0600 Orion Poplawski wrote: > Orion Poplawski wrote: >> Alan W. Irwin wrote: >>> >>> You are the first to report this problem. The python examples certainly >>> work on my two systems (Ubuntu Breezy with Python 2.4.2/Numeric-23.8 and >>> Debian stable with Python 2.3.5/Numeric-23.8). What is your version of >>> Python _and_ Numeric? >> >> Indeed, I don't see the problem on Fedora 5. Devel has python 2.4.3 and >> Numeric 23.7. 5 has python 2.4.2 and Numeric 23.7. I'll poke around some >> more. >> > > Confirmed as an issue with Numeric 23.7 and python 2.4.3. Updating to 24.2 > fixes so I've filed a bug with Fedora to try to get it updated. > > Any plans to move to numpy? Not unless and until it gets better supported by distributions. I just checked Ubuntu dapper packages (which is also effectively a search of Debian unstable), and I can find no sign of it there. Just the older Numeric (which confusingly was called numpy originally which is quite different from the modern NumPy) and NumArray. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |