From: Alan W. I. <ir...@be...> - 2002-09-04 18:29:08
Attachments:
plplotcmodule.c_double
plplotcmodule.c_single
|
Maurice, I just built the plplot (1.5) python interface on RH 7.3 without any problems For example, I can run pythondemos.py in plplot/tmp without any problems. One potentially significant difference from your effort is I used the attached python interface files that I generated with swig on my Debian system. Could you please do the following? (1) See if the attached files work for you. They of course should be placed in bindings/python with the exact names I have given them. The Makefile and the symlinks set up in tmp by configure should take care of the rest. (2) If you also obtain success with those interface files, then please compare them with what is generated by the latest-generation swig you installed on your RH7.3 system, and please let me know what differences there are. Note, most users will have access to the attached files since I will be including them in the release tarball for the next release in bindings/python. It is only cvs users that have to build them for themselves with swig (or use the attached versions until the next tweak of the python interface). I also found there was an itcl installation problem on RH7.3. Once we are on the same page with respect to the python interface, could you look into that? The error messages were: no files matched glob patterns "*.tcl *.itcl *.itk *.ith *.itm" while executing "glob *.tcl *.itcl *.itk *.ith *.itm" ("eval" body line 1) invoked from within "eval glob $args" (procedure "auto_mkindex" line 24) invoked from within "auto_mkindex . *.tcl *.itcl *.itk *.ith *.itm" invoked from within "if {[catch {package require Itcl}]} { # Error including Itcl -- only include tcl files auto_mkindex . *.tcl I currently have no idea where this is coming from and would be most interested in whether the same installation error happens on your RH7.3 machine. Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |
From: Alan W. I. <ir...@be...> - 2002-09-04 20:29:01
|
P.S. My version of swig is 1.3.11-1. The latest swig available at http://prdownloads.sf.net/swig is swig-1.3.14.tar.gz. I presume that is the one you have been trying, but you might want to back off to swig-1.3.11.tar.gz from the same site to see if you replicate my swig generated results in that case. Note, any version less than 1.3.11 will probably not work. Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ On Wed, 4 Sep 2002, Alan W. Irwin wrote: > Maurice, I just built the plplot (1.5) python interface on RH 7.3 without > any problems For example, I can run pythondemos.py in plplot/tmp without any > problems. > > One potentially significant difference from your effort is I > used the attached python interface files that I generated with swig > on my Debian system. Could you please do the following? > > (1) See if the attached files work for you. They of course should be placed > in bindings/python with the exact names I have given them. The Makefile and > the symlinks set up in tmp by configure should take care of the rest. > > (2) If you also obtain success with those interface files, then please > compare them with what is generated by the latest-generation swig you > installed on your RH7.3 system, and please let me know what differences > there are. [...] |
From: Maurice L. <mj...@ga...> - 2002-09-15 19:06:44
|
Alan W. Irwin writes: > Maurice, I just built the plplot (1.5) python interface on RH 7.3 without > any problems For example, I can run pythondemos.py in plplot/tmp without any > problems. > > One potentially significant difference from your effort is I > used the attached python interface files that I generated with swig > on my Debian system. Could you please do the following? > > (1) See if the attached files work for you. They of course should be placed > in bindings/python with the exact names I have given them. The Makefile and > the symlinks set up in tmp by configure should take care of the rest. Hi, I finally got around to doing this, and yes it works! For the first time ever, I am seeing the plplot python bindings in action. :) So the difference is due to the change in version of swig. I am using 1.3.14 currently, so will back off to an older version as you suggested. > (2) If you also obtain success with those interface files, then please > compare them with what is generated by the latest-generation swig you > installed on your RH7.3 system, and please let me know what differences > there are. Lots. But the ones that look to be the likely culprits are: < #define SWIG_init initplplotc < #define SWIG_name "plplotc" > #define SWIG_init init_plplotc > #define SWIG_name "_plplotc" The latter ones are those generated by swig 1.3.14. Ugh. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Alan W. I. <ir...@be...> - 2002-09-16 02:38:09
|
On Sun, 15 Sep 2002, Maurice LeBrun wrote: > [...] For the first time > ever, I am seeing the plplot python bindings in action. :) Great! > < #define SWIG_init initplplotc > < #define SWIG_name "plplotc" > > > #define SWIG_init init_plplotc > > #define SWIG_name "_plplotc" > > The latter ones are those generated by swig 1.3.14. Ugh. Gary and Olof (separately) what version of swig are you using? Alan |
From: Maurice L. <mj...@ga...> - 2002-09-16 03:04:06
|
Maurice LeBrun writes: > Alan W. Irwin writes: > > (2) If you also obtain success with those interface files, then please > > compare them with what is generated by the latest-generation swig you > > installed on your RH7.3 system, and please let me know what differences > > there are. > > Lots. But the ones that look to be the likely culprits are: > > < #define SWIG_init initplplotc > < #define SWIG_name "plplotc" > > > #define SWIG_init init_plplotc > > #define SWIG_name "_plplotc" > > The latter ones are those generated by swig 1.3.14. Ugh. OK, I have built, installed, and tested 1.3.11 through 1.3.15, and found: #define SWIG_init initplplotc #define SWIG_name "plplotc" are used by 1.3.11 - 1.3.13, and #define SWIG_init init_plplotc #define SWIG_name "_plplotc" are used in 1.3.14 & 1.3.15. Since it's in both of the last two versions it would seem to be a convention change and not a bug. Jeez, I'd think this would warrant a major version number change since it's clearly not backward compatible. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Alan W. I. <ir...@be...> - 2002-09-16 04:56:00
|
On Sun, 15 Sep 2002, Maurice LeBrun wrote: > OK, I have built, installed, and tested 1.3.11 through 1.3.15, > and found: > > #define SWIG_init initplplotc > #define SWIG_name "plplotc" > > are used by 1.3.11 - 1.3.13, and > > #define SWIG_init init_plplotc > #define SWIG_name "_plplotc" > > are used in 1.3.14 & 1.3.15. Since it's in both of the last two versions it > would seem to be a convention change and not a bug. Jeez, I'd think this > would warrant a major version number change since it's clearly not backward > compatible. We need the features of swig-1.3.x so we must use it, but it is an unstable release series (like kernel 2.5.x) so you do expect changed features from one 1.3.x release to the next. Also, the pace of change should slow as they converge to the 2.0 version. Earlier this year they hoped to bring that out this month. I don't know how much, if at all, that schedule has slipped. After some searching I just found that the convention change on the leading underscore is explained in http://www.swig.org/Doc1.3/Python.html#n6. Actually, I like that convention because it fits right with our needs to distinguish the extension module name from the python wrapper module name. In fact, Gary and I adopted the 'c' in plplotc for exactly that same reason, but if we had been smarter back then, the underscore prefix would have been a better (IMHO), and I would certainly be happy to adopt it now. I don't know the significance of changing SWIG_init. Gary, can you explain that and/or make swig-1.3.15 work for us? If so, I would be willing to adopt that version in anticipation that it will be an easy step from there to swig-2.0, once that comes out. Alan |
From: Alan W. I. <ir...@be...> - 2002-09-23 20:37:27
|
On Sun, 15 Sep 2002, I previously wrote about the possibility of changing from swig-1.3.1[1-3] to later (e.g., 1.3.15) in the unstable series which will lead to a stable 2.0 version of swig. FYI, I have discussed this with Gary, and neither one of us has the time currently to do the required adaptation to swig-1.3.15. Thus, the decision is to stick with swig-1.3.1[1-3] for now, and I (with possibly some help from Gary) will attempt to do the required adaptation to swig-2.0 when it comes out. So the current status is Gary (RedHat, MacOS X, and windows), I (Debian and RH 7.3), Maurice (RH 7.3), and Olof (windows) have built and used the new python interface with no reported problems using swig-1.3.1[1-3]. In contrast Geoffrey and Joao did have problems presumably because they were using something different from swig-1.3.1[1-3]. Will you guys please try again with a swig version in the required range (1.3.11 works for me), and let me know if there are any problems? Alan |
From: Maurice L. <mj...@ga...> - 2002-09-16 02:31:11
|
Maurice LeBrun writes: > Alan W. Irwin writes: > > Maurice, I just built the plplot (1.5) python interface on RH 7.3 without > > any problems For example, I can run pythondemos.py in plplot/tmp without any > > problems. > > > > One potentially significant difference from your effort is I > > used the attached python interface files that I generated with swig > > on my Debian system. Could you please do the following? > > > > (1) See if the attached files work for you. They of course should be placed > > in bindings/python with the exact names I have given them. The Makefile and > > the symlinks set up in tmp by configure should take care of the rest. > > Hi, I finally got around to doing this, and yes it works! For the first time > ever, I am seeing the plplot python bindings in action. :) > > So the difference is due to the change in version of swig. I am using > 1.3.14 currently, so will back off to an older version as you suggested. Stranger and stranger. Having built and installed 1.3.11 on my system, I do not get the result you did. So far I've tried: 1.3.11, 1.3.14, 1.3.15, and they all give the same result. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Maurice L. <mj...@ga...> - 2002-09-16 02:35:34
|
Maurice LeBrun writes: > Maurice LeBrun writes: > > Alan W. Irwin writes: > > > Maurice, I just built the plplot (1.5) python interface on RH 7.3 without > > > any problems For example, I can run pythondemos.py in plplot/tmp without any > > > problems. > > > > > > One potentially significant difference from your effort is I > > > used the attached python interface files that I generated with swig > > > on my Debian system. Could you please do the following? > > > > > > (1) See if the attached files work for you. They of course should be placed > > > in bindings/python with the exact names I have given them. The Makefile and > > > the symlinks set up in tmp by configure should take care of the rest. > > > > Hi, I finally got around to doing this, and yes it works! For the first time > > ever, I am seeing the plplot python bindings in action. :) > > > > So the difference is due to the change in version of swig. I am using > > 1.3.14 currently, so will back off to an older version as you suggested. > > Stranger and stranger. Having built and installed 1.3.11 on my system, I do > not get the result you did. So far I've tried: 1.3.11, 1.3.14, 1.3.15, and > they all give the same result. AAAHHH.. bogus. Sorry, ignore, path problems. My built version of 1.3.11 *does* give the same result as you got. Now testing the others. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Maurice L. <mj...@ga...> - 2002-09-16 21:50:29
|
Alan W. Irwin writes: > I also found there was an itcl installation problem on RH7.3. Once we > are on the same page with respect to the python interface, could you look > into that? The error messages were: > > no files matched glob patterns "*.tcl *.itcl *.itk *.ith *.itm" > while executing > "glob *.tcl *.itcl *.itk *.ith *.itm" > ("eval" body line 1) > invoked from within > "eval glob $args" > (procedure "auto_mkindex" line 24) > invoked from within > "auto_mkindex . *.tcl *.itcl *.itk *.ith *.itm" > invoked from within > "if {[catch {package require Itcl}]} { > > # Error including Itcl -- only include tcl files > auto_mkindex . *.tcl > > I currently have no idea where this is coming from and would be most > interested in whether the same installation error happens on your RH7.3 > machine. This really shouldn't be happening -- it means there were no *.tcl files in the installed tcl directory. Which doesn't make sense if you have configured tcl in (and if you haven't, this won't be run). <shrug> oh well, I silenced the unlikely error with a catch {} and also took the opportunity to fix a year-old item on my todo list about tying mktclIndex to the configuration info. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |