Re: [Plplot-devel] Status of release testing

2009-01-20 Thread Werner Smekal
Hi Arjen, > > I will have a look at the gnuwin32 packages you mentioned and see > whether I can get the missing > tools from there. could you exactly write down which packages you need to get this going? I already have a lot of these packages installed, but it would be good to know what the

Re: [Plplot-devel] Status of release testing

2009-01-19 Thread Alan W. Irwin
On 2009-01-19 11:01+0100 Werner Smekal wrote: > Hi, > >> >> Well, that does sound as a reasonable and little-work solution. >> As CMake warns about not being able to find bash and therefore ctest >> won't work, I thought that using MinGW might get me around this >> problem. >> But undoubtedly that

Re: [Plplot-devel] Status of release testing

2009-01-19 Thread Werner Smekal
Hi, > > Well, that does sound as a reasonable and little-work solution. > As CMake warns about not being able to find bash and therefore ctest > won't work, I thought that using MinGW might get me around this > problem. > But undoubtedly that introduces new ones and it changes the platform > in

Re: [Plplot-devel] Status of release testing

2009-01-19 Thread Arjen Markus
> Hi Arjen: > > The current set of shell scripts for testing have had constant maintenance > and improvement as long as I can remember. So I think taking a windows > batch file approach to do the same thing would create a substantial > maintenance issue that we should avoid if at all possible. > >

Re: [Plplot-devel] Status of release testing

2009-01-19 Thread Alan W. Irwin
On 2009-01-19 08:52+0100 Arjen Markus wrote: > > It is a pity that I cannot use these testing scripts under plain Windows. > One addtional thing to do: create batch files that will do the same > thing (or at least approximate the shell scripts). Hi Arjen: The current set of shell scripts for tes

Re: [Plplot-devel] Status of release testing

2009-01-18 Thread Arjen Markus
> On 2009-01-16 23:10-0800 Alan W. Irwin wrote: > .. > I am concerned the script update is so close to our release deadline it > makes it difficult for anybody to test it before the release, but please > try to do so before the release by running > > "make test_interactive" > > or > > ./make ; ./p

Re: [Plplot-devel] Status of release testing

2009-01-17 Thread Alan W. Irwin
On 2009-01-16 23:10-0800 Alan W. Irwin wrote: > The only release-critical issue I am aware of at the present time is a > segfault I discovered a day ago when I ran > > softw...@raven> c++/wxPLplotDemo > Segmentation fault I am glad to report Werner's latest commit solved this issue. I also took

Re: [Plplot-devel] Status of release testing

2009-01-16 Thread Alan W. Irwin
On 2009-01-15 17:55-0800 Alan W. Irwin wrote: > In sum, for my Debian testing platform and Orion's Fedora platform we are > essentially ready to release although there are still some well-known issues > discovered for the last release that "would-be-nice" to fix for this > release. It appears we

Re: [Plplot-devel] Status of release testing

2009-01-16 Thread Alan W. Irwin
On 2009-01-16 13:54- Andrew Ross wrote: > Alan, > > I think I have now fixed this one. h2def.py did not understand the > PLDLLIMPEXP macros in plplotcanvas.h. Stripping these out with sed before > processing means the python plplotcanvas bindings are generated > correctly again. I get a load o

Re: [Plplot-devel] Status of release testing

2009-01-16 Thread Andrew Ross
On Thu, Jan 15, 2009 at 05:55:16PM -0800, Alan Irwin wrote: > > I tried testing the > optimized case for default hidden visibility by setting > > softw...@raven> export CC='gcc -fvisibility=hidden -O2' > softw...@raven> export CXX='g++ -fvisibility=hidden -O2' > softw...@raven> export FC='gfort

Re: [Plplot-devel] Status of release testing

2009-01-16 Thread Arjen Markus
> The status of testing for this forthcoming release is as follows: > > * I have recently confirmed the segfaults are still there for all our > Tk-related examples, but not for -dev tk. I have updated README.release > accordingly. That notice should be removed if somebody can figure this > out.