On dimanche 2 juillet 2017 23:09:14 CEST Even Rouault wrote:
> > However, if I add -std=gnu++11 or -std=c++11 to the compile line for
> > these files, then they compile without warning or error.  The
> > whole gdal build and install then completes.
> > 
> > -std=gnu++03 and -std=c++03 do not resolve the error, so I wonder
> > whether we have accidentally added a dependancy for C++13 in 2.1.4 ?
> 
> This is more subtle than that. I guess this is due to a security update of
> Jasper itself that brings use of SIZE_MAX in Jasper include files. However
> in RHEL 6, SIZE_MAX from stdint.h is only defined if __cplusplus is not
> defined. But I guess that in C++11 mode SIZE_MAX is defined as mandated by
> C++11...
> 
> Anyway this is now fixed per
> https://trac.osgeo.org/gdal/ticket/6951

Forgot to mention that our Travis-CI configurations are all Ubuntu-based. 
Someone wanting 
primer RHEL/CentOS/Scientific Linux support could contribute a new 
configuration using a 
CentOS-based Docker image in a Travis-CI Ubuntu Trusty host.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to