On Mar 4, 2010, at 17:30 , Alan W. Irwin wrote:

> On 2010-03-04 16:25-0800 David MacMahon wrote:
>
>> octave
>> Missing examples            :  19
>> Differing postscript output :  28 29
>> Missing stdout              :
>> Differing stdout            :  14
>> tcl
>> Missing examples            :
>> Differing postscript output :  21 28
>> Missing stdout              :
>> Differing stdout            :  21
>
> Those are the expected results.  The "glass is 99.6 per cent full" way
> to look at this is 99.6 per cent of our bindings/examples produce
> identical PostScript results to our C versions which is a terrific
> achievement.

Yes, I agree!  FWIW, the octave and tcl postscript output for x28  
match (other than CreationDate).  It looks like maybe those examples  
got left out during this set of changes...

r10789 Propagate recent example 28 fixes to OCaml
r10710 Propagate C changes for example 28 to the corresponding Lua  
example.
r10709 Propagate C changes for example 28 to the corresponding Python  
example.
r10708 Propagate C changes to example 28 to the corresponding f77 and  
f95 examples.
r10699 Propagate C changes to example 28 to the corresponding C++, D,  
and Java versions.
r10697 Commit prototype changes to the C example to improve the  
appearance of pages 2 and 3. These changes need to be propagated to  
all the remaining language examples.

>> I ran make test_interactive, but it gets to...
>>
>> [ 97%] Built target test_c_xcairo
>> [100%] Built target tk
>> Generate C results for tk interactive device
>> Testing subset of C examples for device tk
>> x01c
>>
>> ...and then appears to hang there.  I get an empty plserver  
>> window, but don't know what to do at that point, so I wait a while  
>> and then ctrl-c which stops the test sequence.
>>
>> Any pointers?
>
> However, you may want to put this Tk issue aside (-DENABLE_tk=OFF
> -DPLD_tk=OFF) for now and instead concentrate on testing your 2D  
> patch for
> the non-Tk case now so we can move forward with that.
>
> Your choice as to what you do first.  Either would be quite a help to
> us.

I'm looking into some possible conflicts between system tcl/tk and  
macports tcl/tk...

Dave


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to