Hi Ed,

I found a little time to look at this again.

I activated proj @4.9.1 in Macports:

$ port installed proj
The following ports are currently installed:
  proj @4.8.0_1
  proj @4.9.1_0 (active)

1) On branch master at commit d9a474e, during Makefile.PL, I get 

Building PDL::GIS::Proj. Turn off WITH_PROJ if there are any problems
Unrecognized argument in LIBS ignored: '"-L/opt/local/lib"'

and 

Building PDL::Transform::Proj4. Turn off WITH_PROJ if there are any problems
Unrecognized argument in LIBS ignored: '"-L/opt/local/lib"'

I ignored that and proceeded with 'make'.

2) I don't see any reference to Alien modules when compiling. PDL::GIS::Proj 
and PDL::Transform::Proj4 compile normally—it looks like it always has, and 
make test passes just fine too.

These results are the same when I use MacPorts' proj @4.8.0_1.  So I'm happy 
with this.

Thanks!

Derek


> On Apr 3, 2015, at 1:08 PM, Ed <ej...@hotmail.com> wrote:
> 
> Rob, great news. Thanks for the help.
> 
> Seems to me that a conflict between MinGW and Proj is outside the scope of 
> PDL, therefore it seems to me like this branch now definitely represents 
> progress/reduced regression, therefore I have merged it.
> 
> Chris, since Travis has already Okay-ed it on its branch, what do you think 
> of another release-candidate release?
> 
> Ed
> 
> -----Original Message----- 
> From: sisyph...@optusnet.com.au
> Sent: Thursday, April 02, 2015 2:23 AM
> To: Ed
> Cc: pdl-devel
> Subject: Re: [Pdl-devel] Proj presently broken
> 
> -----Original Message----- 
> From: Ed
> Sent: Thursday, April 02, 2015 10:18 AM
> To: sisyph...@optusnet.com.au
> Cc: pdl-devel
> Subject: Re: [Pdl-devel] Proj presently broken
> 
>> Good spot on the $include_path. Additional commit pushed on the projfixp2 
>> branch, should just work. Rob, does it work for you?
> 
> Yep - works good.
> 
>> Oddly now on my Win32 system I'm getting conflicts between PVALUE in MinGW 
>> and in Proj4, which Rob I see you asked about a long while ago?
> 
> I was hoping that they'd rename PVALUE to something that doesn't clash, but
> they haven't. My recollection is that, when I reported this issue to the
> proj mailing list, the response was "gee, that's unfortunate".
> Not sure how kmx dealt with this for his 64-bit builds (32-bit builds are
> unaffected AFAIK), but I've been working around it by altering the proj
> source to replace all occurrences of PVALUE  with _P_VALUE.
> "PVALUE" is found in about 3 or 4 places in the source, spread over 2 files
> (projects.h and pj_param.c) - so it's a hack that doesn't take long to
> implement.
> 
> It might be that projects.h merely needs to begin with:
> 
> #ifdef PVALUE
> #undef PVALUE
> #endif
> 
> I haven't tested that.
> 
> Cheers,
> Rob
> 
> 
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> pdl-devel mailing list
> pdl-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pdl-devel
> 


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel

Reply via email to