From: Alan W. I. <ir...@be...> - 2016-11-23 00:50:21
|
Tom Schoonjans made some good points on plplot-general about officially releasing timely fixes for PLplot rather than expecting packagers and others to dig those out of git, and I also feel it is critical to give our users good access to the recent big improvements in both our Fortran and Tcl bindings. So to answer these concerns my plan is to release PLplot-5.12.0 on ********** December 17th **********. That is roughly the last release date possible in December without intruding on Christmas holiday time, and I don't want to put off this release until January for the above reasons. Note, I don't want the release any sooner than the above date because there are a lot of (fairly minor) topics I am still working on that I would like to get into this release. Therefore, I plan to continue working on those topics for the rest of this week and the next one and declare a soft freeze (where only minor bug fixing and documentation improvements should occur after that freeze date until the release) on ********** December 3rd **********. That freeze date should give us two weeks for extensive testing of PLplot (and fixing all bugs that are turned up by such testing) on all platforms accessible to PLplot developers and users. (Note, I do plan to ask our users on plplot-general to help with testing during those two critical weeks on the platforms accessible to them.) Please speak out if either of the two dates above need an adjustment from your perspective. For example, another freeze date alternative could be December 10th (which still gives us the minimum one week of time we need for testing). But that freeze date would be completely inflexible, and I would prefer a more flexible freeze date (to accommodate last-minute requests to change it for those developers who discover they need a few more days to get their topics merged) which is why I have suggested December 3rd as the freeze date. If nobody has any suggestions for changes in the above two critical dates by (say) late Wednesday I will follow up by announcing the above two critical dates on PLplot-general. Alan (your friendly release manager). __________________________ 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 __________________________ |
From: Pedro V. <ped...@sp...> - 2016-11-23 01:21:47
|
Hi Alan Those dates look good to me, and I will investigate my 3 thread issues (wxWidgets, Qt, error messages ) well before the freezing date -Pedro ----- Original Message ----- From: "Alan W. Irwin" <ir...@be...> To: "PLplot development list" <Plp...@li...> Sent: Tuesday, November 22, 2016 7:50 PM Subject: [Plplot-devel] Soft freeze on December 3rd and release on December17th? > Tom Schoonjans made some good points on plplot-general about > officially releasing timely fixes for PLplot rather than expecting > packagers and others to dig those out of git, and I also feel it is > critical to give our users good access to the recent big improvements > in both our Fortran and Tcl bindings. So to answer these concerns my > plan is to release PLplot-5.12.0 on ********** December 17th **********. > That is roughly the last release date possible in December without > intruding on Christmas holiday time, and I don't want to put off this > release until January for the above reasons. > > Note, I don't want the release any sooner than the above date because > there are a lot of (fairly minor) topics I am still working on that I > would like to get into this release. Therefore, I plan to continue > working on those topics for the rest of this week and the next one and > declare a soft freeze (where only minor bug fixing and documentation > improvements should occur after that freeze date until the release) on > ********** December 3rd **********. That freeze date should give us > two weeks for extensive testing of PLplot (and fixing all bugs that > are turned up by such testing) on all platforms accessible to PLplot > developers and users. (Note, I do plan to ask our users on > plplot-general to help with testing during those two critical weeks on > the platforms accessible to them.) > > Please speak out if either of the two dates above need an adjustment > from your perspective. For example, another freeze date alternative > could be December 10th (which still gives us the minimum one week of > time we need for testing). But that freeze date would be completely > inflexible, and I would prefer a more flexible freeze date (to > accommodate last-minute requests to change it for those developers who > discover they need a few more days to get their topics merged) which > is why I have suggested December 3rd as the freeze date. > > If nobody has any suggestions for changes in the above two critical > dates by (say) late Wednesday I will follow up by announcing the above > two critical dates on PLplot-general. > > Alan (your friendly release manager). > __________________________ > 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 > __________________________ > > ------------------------------------------------------------------------------ > _______________________________________________ > Plplot-devel mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-devel > |
From: Alan W. I. <ir...@be...> - 2016-11-23 11:21:00
|
On 2016-11-22 20:21-0500 Pedro Vicente wrote: > Hi Alan > Those dates look good to me, and I will investigate my 3 thread issues > (wxWidgets, Qt, error messages ) well before the freezing date Hi Pedro: Glad those dates work out for you. If as a result of your investigations you have a PLplot change you would like to suggest, then an ordinary compressed patch (which can be generated by "git diff" and "gzip") is an OK way for you to communicate that change to us (as an attachment to your post to this mailing list), but ideally to give you credit for the actual commit we suggest you use "git format-patch" (and "gzip") instead. 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 __________________________ |
From: Pedro V. <ped...@sp...> - 2016-12-09 16:38:50
|
Hi Alan I get an error on the script ERROR: cmake in the build tree failed what I did (CentOS 6.8) git clone http://git.code.sf.net/p/plplot/plplot plplot-plplot cd plplot-plplot/scripts ./comprehensive_test.sh then I tried mkdir build cd build cmake .. make and I get a compiling error , below it seems it's related to wxwidgets-3.1.0 library Note: 1) >>>Essentially all you have to do is set up >>>the relevant environment variables that you normally use to build >>> PLplot I never did set any environment variables to build PLplot before, which ones? 2) I just used cmake .. with no options usually I do with options (no problems) but I just wanted to try like this I can provide further debug output, let me know to which email address should I send to error is [ 16%] Building C object src/CMakeFiles/plplot.dir/__/drivers/xfig.c.o [ 16%] Building C object src/CMakeFiles/plplot.dir/__/drivers/xwin.c.o [ 17%] Linking CXX shared library libplplot.so /usr/bin/ld: /data/data127/pvicente/install/wxwidgets-3.1.0/lib/libwx_gtk2u_core-3.1.a(corelib_event.o): relocation R_X86_64_32 against `wxCommandEvent::ms_classInfo' can not be used when making a shared object; recompile with -fPIC /data/data127/pvicente/install/wxwidgets-3.1.0/lib/libwx_gtk2u_core-3.1.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [src/libplplot.so.13.1.2] Error 1 make[1]: *** [src/CMakeFiles/plplot.dir/all] Error 2 make: *** [all] Error 2 On 2016-11-22 19:50, Alan W. Irwin wrote: > Tom Schoonjans made some good points on plplot-general about > officially releasing timely fixes for PLplot rather than expecting > packagers and others to dig those out of git, and I also feel it is > critical to give our users good access to the recent big improvements > in both our Fortran and Tcl bindings. So to answer these concerns my > plan is to release PLplot-5.12.0 on ********** December 17th > **********. > That is roughly the last release date possible in December without > intruding on Christmas holiday time, and I don't want to put off this > release until January for the above reasons. > > Note, I don't want the release any sooner than the above date because > there are a lot of (fairly minor) topics I am still working on that I > would like to get into this release. Therefore, I plan to continue > working on those topics for the rest of this week and the next one > and > declare a soft freeze (where only minor bug fixing and documentation > improvements should occur after that freeze date until the release) > on > ********** December 3rd **********. That freeze date should give us > two weeks for extensive testing of PLplot (and fixing all bugs that > are turned up by such testing) on all platforms accessible to PLplot > developers and users. (Note, I do plan to ask our users on > plplot-general to help with testing during those two critical weeks > on > the platforms accessible to them.) > > Please speak out if either of the two dates above need an adjustment > from your perspective. For example, another freeze date alternative > could be December 10th (which still gives us the minimum one week of > time we need for testing). But that freeze date would be completely > inflexible, and I would prefer a more flexible freeze date (to > accommodate last-minute requests to change it for those developers > who > discover they need a few more days to get their topics merged) which > is why I have suggested December 3rd as the freeze date. > > If nobody has any suggestions for changes in the above two critical > dates by (say) late Wednesday I will follow up by announcing the > above > two critical dates on PLplot-general. > > Alan (your friendly release manager). > __________________________ > 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 > __________________________ > > > ------------------------------------------------------------------------------ > _______________________________________________ > Plplot-devel mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-devel -- Pedro Vicente ped...@sp... http://www.space-research.org/ |
From: Alan W. I. <ir...@be...> - 2016-12-09 22:05:24
|
On 2016-12-09 11:38-0500 Pedro Vicente wrote: > > Hi Alan > > I get an error on the script > > ERROR: cmake in the build tree failed > > what I did (CentOS 6.8) > > git clone http://git.code.sf.net/p/plplot/plplot plplot-plplot > cd plplot-plplot/scripts > ./comprehensive_test.sh Please look in the prefix directory (by default that is ../comprehensive_test_disposable relative to the top of the source tree) for the report tarball, comprehensive_test.tar.gz, and send that tarball (on or off list) to me. That should allow me to find out why that cmake invocation failed for you, and give you some recommendations about running this test again. > then I tried > > mkdir build > cd build > cmake .. > make This is already a big difference with your comprehensive test result above because cmake succeeded here but not there. But I will know a lot more once I receive the above report tarball from you that is generated by the comprehensive test. > Note: > > 1) > >>>> Essentially all you have to do is set up >>>> the relevant environment variables that you normally use to build >>>> PLplot > > > I never did set any environment variables to build PLplot before, which > ones? It depends on your individual needs. I like to test PLplot with certain compiler options so I typically set export CFLAGS='-O3 -fvisibility=hidden -Wuninitialized' export CXXFLAGS='-O3 -fvisibility=hidden -Wuninitialized' export FFLAGS='-O3 -Wuninitialized -Wunused' But when debugging issues I reduce those to export CFLAGS='-g' export CXXFLAGS='-g' export FFLAGS='-g' Also, I generally find setting the environment variables PATH, CMAKE_INCLUDE_PATH, CMAKE_LIBRARY_PATH, and PKG_CONFIG_PATH are often a big help if cmake is having trouble finding software installed in non-standard locations. > I can provide further debug output, let me know to which email address > should I send to I would prefer to work with your results for the comprehensive test script since that often supplies me with all the information I need to answer your questions. In this case, that script did not get very far the first time you invoked it, but once I see that report tarball, I can likely advise you what simple fix to make so that cmake completes without errors, which means your next comprehensive test run should get to this current build problem concerning wxwidgets with all the information I need, and we can take it from there. 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 __________________________ |
From: Pedro V. <ped...@sp...> - 2016-12-09 22:59:53
Attachments:
comprehensive_test.tar.gz
|
Hi Alan comprehensive_test.tar.gz is attached > export CFLAGS='-g' > export CXXFLAGS='-g' > export FFLAGS='-g' ok, I see I thought you meant environment variables specific for PLplot to build. These are gcc compiler flags, personally I never set them this way, but instead I do it for each makefile. In this build they are the above environment variables thanks -Pedro ----- Original Message ----- From: "Alan W. Irwin" <ir...@be...> To: "Pedro Vicente" <ped...@sp...> Cc: <plp...@li...> Sent: Friday, December 09, 2016 5:05 PM Subject: Re: [Plplot-devel] Soft freeze on December 3rd and release on December 17th? > On 2016-12-09 11:38-0500 Pedro Vicente wrote: > >> >> Hi Alan >> >> I get an error on the script >> >> ERROR: cmake in the build tree failed >> >> what I did (CentOS 6.8) >> >> git clone http://git.code.sf.net/p/plplot/plplot plplot-plplot >> cd plplot-plplot/scripts >> ./comprehensive_test.sh > > Please look in the prefix directory (by default that is > ../comprehensive_test_disposable relative to the top > of the source tree) for the report tarball, comprehensive_test.tar.gz, > and send that tarball (on or off list) to me. That should allow me to > find out why that cmake invocation failed for you, and give you > some recommendations about running this test again. > > >> then I tried >> >> mkdir build >> cd build >> cmake .. >> make > > This is already a big difference with your comprehensive test result > above because cmake succeeded here but not there. But I will know > a lot more once I receive the above report tarball from you that > is generated by the comprehensive test. > >> Note: >> >> 1) >> >>>>> Essentially all you have to do is set up >>>>> the relevant environment variables that you normally use to build >>>>> PLplot >> >> >> I never did set any environment variables to build PLplot before, which >> ones? > > It depends on your individual needs. I like to test PLplot with certain > compiler options so I typically set > > export CFLAGS='-O3 -fvisibility=hidden -Wuninitialized' > export CXXFLAGS='-O3 -fvisibility=hidden -Wuninitialized' > export FFLAGS='-O3 -Wuninitialized -Wunused' > > But when debugging issues I reduce those to > > export CFLAGS='-g' > export CXXFLAGS='-g' > export FFLAGS='-g' > > Also, I generally find setting the environment variables PATH, > CMAKE_INCLUDE_PATH, CMAKE_LIBRARY_PATH, and PKG_CONFIG_PATH are often > a big help if cmake is having trouble finding software installed in > non-standard locations. > >> I can provide further debug output, let me know to which email address >> should I send to > > I would prefer to work with your results for the comprehensive test > script since that often supplies me with all the information I need to > answer your questions. In this case, that script did not get very far > the first time you invoked it, but once I see that report tarball, I > can likely advise you what simple fix to make so that cmake completes > without errors, which means your next comprehensive test run should > get to this current build problem concerning wxwidgets with all the > information I need, and we can take it from there. > > 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 > __________________________ > |
From: Pedro V. <ped...@sp...> - 2016-12-09 23:02:36
|
ok, simple issue , ignore I tool a quick look at the ouput , it's just CMake 3.0.2 or higher is required. You are running version 2.8.12.2 ----- Original Message ----- From: "Alan W. Irwin" <ir...@be...> To: "Pedro Vicente" <ped...@sp...> Cc: <plp...@li...> Sent: Friday, December 09, 2016 5:05 PM Subject: Re: [Plplot-devel] Soft freeze on December 3rd and release on December 17th? > On 2016-12-09 11:38-0500 Pedro Vicente wrote: > >> >> Hi Alan >> >> I get an error on the script >> >> ERROR: cmake in the build tree failed >> >> what I did (CentOS 6.8) >> >> git clone http://git.code.sf.net/p/plplot/plplot plplot-plplot >> cd plplot-plplot/scripts >> ./comprehensive_test.sh > > Please look in the prefix directory (by default that is > ../comprehensive_test_disposable relative to the top > of the source tree) for the report tarball, comprehensive_test.tar.gz, > and send that tarball (on or off list) to me. That should allow me to > find out why that cmake invocation failed for you, and give you > some recommendations about running this test again. > > >> then I tried >> >> mkdir build >> cd build >> cmake .. >> make > > This is already a big difference with your comprehensive test result > above because cmake succeeded here but not there. But I will know > a lot more once I receive the above report tarball from you that > is generated by the comprehensive test. > >> Note: >> >> 1) >> >>>>> Essentially all you have to do is set up >>>>> the relevant environment variables that you normally use to build >>>>> PLplot >> >> >> I never did set any environment variables to build PLplot before, which >> ones? > > It depends on your individual needs. I like to test PLplot with certain > compiler options so I typically set > > export CFLAGS='-O3 -fvisibility=hidden -Wuninitialized' > export CXXFLAGS='-O3 -fvisibility=hidden -Wuninitialized' > export FFLAGS='-O3 -Wuninitialized -Wunused' > > But when debugging issues I reduce those to > > export CFLAGS='-g' > export CXXFLAGS='-g' > export FFLAGS='-g' > > Also, I generally find setting the environment variables PATH, > CMAKE_INCLUDE_PATH, CMAKE_LIBRARY_PATH, and PKG_CONFIG_PATH are often > a big help if cmake is having trouble finding software installed in > non-standard locations. > >> I can provide further debug output, let me know to which email address >> should I send to > > I would prefer to work with your results for the comprehensive test > script since that often supplies me with all the information I need to > answer your questions. In this case, that script did not get very far > the first time you invoked it, but once I see that report tarball, I > can likely advise you what simple fix to make so that cmake completes > without errors, which means your next comprehensive test run should > get to this current build problem concerning wxwidgets with all the > information I need, and we can take it from there. > > 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 > __________________________ > |
From: Alan W. I. <ir...@be...> - 2016-12-10 13:08:55
|
On 2016-12-09 18:02-0500 Pedro Vicente wrote: > ok, simple issue , ignore > > I tool a quick look at the ouput , it's just > > > CMake 3.0.2 or higher is required. You are running version 2.8.12.2 OK. So please fix that (run scripts/comprehensive_test.sh --help to see how to specify the cmake command exactly). Once you run scripts/comprehensive_test.sh with the correct cmake, then as I suggested before please follow up by sending me the report tarball to help figure out what is wrong for the wxwidgets case on CentOS. 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 __________________________ |
From: Alan W. I. <ir...@be...> - 2016-12-10 13:18:34
|
On 2016-12-10 05:08-0800 Alan W. Irwin wrote: > On 2016-12-09 18:02-0500 Pedro Vicente wrote: > >> ok, simple issue , ignore >> >> I tool a quick look at the ouput , it's just >> >> >> CMake 3.0.2 or higher is required. You are running version 2.8.12.2 > > OK. So please fix that (run scripts/comprehensive_test.sh --help to > see how to specify the cmake command exactly). Once you run > scripts/comprehensive_test.sh with the correct cmake, then as I > suggested before please follow up by sending me the report tarball to > help figure out what is wrong for the wxwidgets case on CentOS. Never mind. I should have checked my incoming mail first to see you have gone another way. But in general, creating a report tarball is a good way to report errors since it gives all sorts of details that otherwise are a pain to collect consistently for an error report. 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 __________________________ |