I think a combination of the PDL-2.4.10 version
of Proj.pd with the new code for 4.8.0 implemented
with appropriate #ifdefs on PROJ4 version should
work with old and new proj installs since it would
use the current stable implementation for pre-4.8.0
verions of libproj and then the new code for more
recent versions.
--Chris
On 4/8/2012 9:36 AM, chm wrote:
On 4/8/2012 8:25 AM, Sisyphus wrote:
----- Original Message ----- From: "Sisyphus"
I've just re-built and installed 4.7.0 and built PDL-2.4.10_003
against it ( but using my *patched* Proj.pd instead of the crappy
Proj.pd that ships with 2.4.10_003) ... no problems there ... I'll
give 4.6.1 a go and see what happens.
As near as I can tell, there was only one change
between the PDL-2.4.10 and the PDL-2.4.10_001
Proj.pd. The Proj.pd in PDL-2.4.10_003 should be
the one from PDL-2.4.10.
Can't find any problem using 4.6.1 with my patched Proj.pd file.
Could you post the actual Proj.pd that you used, along with the exact
error messages that were presented ?
Here is a test report from _001 showing the crash
in the build for the proj stuff:
http://www.cpantesters.org/cpan/report/3b9ea826-7ff9-11e1-859e-be2e173997d5
I'm hoping that the two other problems in the
PDL-2.4.10_001 release (the Proj.pd problems and
fails in t/gd_oo_tests.t) may have been side
effects of the low level change to the PDL core
routines.
Early testing for PDL-2.4.10_003 looks pretty
good and if that continues, we can add the new
Prod.pd code and see how that works. I'll try
a clean build on my systems with _003 plus the
re-reverted Proj.pd as well.
Cheers,
Chris
Cheers,
Rob
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2409/4922 - Release Date: 04/08/12
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
