On Apr 19, 2014, at 7:44 PM, Even Rouault wrote:
> Selon William Kyngesburye :
>
>> On Apr 19, 2014, at 2:56 PM, Even Rouault
>> wrote:
>>
>>> 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 b
Selon William Kyngesburye :
> On Apr 19, 2014, at 2:56 PM, Even Rouault
> wrote:
>
> > 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
On Apr 19, 2014, at 2:56 PM, Even Rouault wrote:
> 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 reporti
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 ch
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 stacko
Hi,
I've noticed that since a few days our Travis-CI MacOS X job has started to
fail building the Python bindings.
The last successfull build was
https://travis-ci.org/rouault/gdal_coverage/builds/22998284 with
i386-apple-darwin12.5.0 (MacOSX 10.8)
The current build ( https://travis-ci.org/rou
Le vendredi 18 avril 2014 23:37:47, Martin Landa a écrit :
> Hi,
>
> 2014-04-18 19:43 GMT+02:00 Even Rouault :
> > I've switched to 1.12dev
>
> thanks, but how is possible that after running configure this file is
> changed
>
> Index: VERSION
> ===
