[PROJ] PROJ 6.0.0RC3

[Kristian Evers]

Are we at a point now where we say if this is a problem local to Greg’s setup
or if this is a general problem in PROJ that needs fixing?

/Kristian

> On 26 Feb 2019, at 16:09, Even Rouault <even.rouault at spatialys.com> wrote:
> 
>> (The machine also has gcc 6 installed, in a different prefix, but no older
>> versions.)
>> 
>> I would hope that proj builds ok with gcc 4.8; haven't tried yet.
> 
> It does.
> 
>> 
>>> If that's indeed the only file to fail compilation, I'd suggest you try
>>> tweaking the start of the file to comment out the #define _XOPEN_SOURCE
>>> 500
>>> and/or #define _GNU_SOURCE
>> 
>> That was the only one.  It makes sense then that the --std flag is not
>> the issue.  Thanks for those hints - I had forgotten about
>> _XOPEN_SOURCE, but now that I remember about definition visibility
>> controls it sounds promising.
>> 
>> 
>> 
>> Has anyone built proj 6 with clang?  Any success reports from other than
>> Linux?
> 
> It is built on different number of configurations in
> https://travis-ci.com/OSGeo/proj.4/
> and
> https://travis-ci.com/OSGeo/gdal
> 
> Including clang and macosx
> 
> Windows Visual Studio builds also per
> https://ci.appveyor.com/project/OSGeo/proj-4/history
> 
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com