> Maybe there is something weird in the Travis system.
They must have changed something to fix it, since builds now pass.
>
> -
> William Kyngesburye
> http://www.kyngchaos.com/
>
> "Time is an illusion - lunchtime doubly so."
>
> - Ford Prefect
--
Geospatial professional services
htt
On Apr 20, 2014, at 4:39 AM, Even Rouault wrote:
>> Well, you could try leaving out the os.uname test. clang is clang no matter
>> what version of OS X, and it wouldn't hurt to include the option when it's
>> already default. Also, testing the OS version doesn't necessarily say what
>> clang v
http://en.wikipedia.org/wiki/Xcode#Composition says that clang started at
xcode 4.2, for which the version numbering is decoupled from the darwin
version. There are two tables at the bottom that only sort of tell the
whole story...
http://en.wikipedia.org/wiki/Xcode#Versions_compare_table
e.g. o
> Well, you could try leaving out the os.uname test. clang is clang no matter
> what version of OS X, and it wouldn't hurt to include the option when it's
> already default. Also, testing the OS version doesn't necessarily say what
> clang version is installed.
Could you try leaving out test os.
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
10 matches
Mail list logo
