Le samedi 19 avril 2014 21:19:53, William Kyngesburye a écrit : > It looks like a bit of a coordination and packaging snafu with Apple. > Apple builds Python with some old flags that clang doesn't support, but > clang defaulted to NOT reporting the unknown flag as error. The recent > clang 5.1 changed this default to error. > > I found a discussion about it on stackoverflow: > > http://stackoverflow.com/questions/22313407/clang-error-unknown-argument-mn > o-fused-madd-python-package-installation-fa > > The -Qunused-arguments trick seems to work for some and not others. There > is another method to try (the error actually mentions it): add this to > ARCHFLAGS: > > -Wno-error=unused-command-line-argument-hard-error-in-future
I've not access to a Mac myself, only through Travis, which is highly inconvenient for trial and error attempts. Perhaps you or someone with direct access to a system that exhibits the issue can come up with a patch ? -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
