Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#47299 closed enhancement (fixed)

Update Xcode on buildbot builders

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: admin@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc: mojca (Mojca Miklavec)
Port:

Description

Could you please check on the 10.7 and 10.8 buildbot builders which versions of Xcode and the Xcode command line tools are installed, and update them if they're outdated? I'd like them to be at the latest versions. For the 10.7 builder that would be Xcode 4.6.3, and for the 10.8 builder that would be Xcode 5.1.1. After updating Xcode, the corresponding Xcode command line tools should be installed. If you're installing Xcode via the Mac App Store, the command line tools update may simply be suggested in the App Store updates. If you're installing Xcode by manually downloading it from the Apple developer web site, then you'll need to manually download and install the corresponding command line tools. If you need help identifying which version that is, let me know and I'll look it up.

Change History (5)

comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Henry says:

I show running /usr/bin/xcodebuild -verison on the 10.7 builder is Xcode 4.6.3 and build version 4H1503 for 10.8 I am showing Xcode 5.1.1 build version 5B1008

Mojca: can you remind me how you determined that the 10.8 builder was not running Xcode 5.1.1? I'm wondering if maybe the Xcode app is up to date but the command line tools are not, or vice versa.

comment:2 Changed 10 years ago by mojca (Mojca Miklavec)

The original problem was reported in #47273, this was the particular failed build:

If you check compile -> stdio logs from "any given" build on the Mountain Lion buildbot, you'll see the following line:

DEBUG: compiler clang 421.11.66 not blacklisted because it doesn't match {clang < 211.10.1}

while it's OK on Lion:

DEBUG: compiler clang 425.0.28 not blacklisted because it doesn't match {clang < 211.10.1}

This was confirmed after I blacklisted clang < 425, the buildbot used macports-clang-3.4 and the build succeeded. On Lion the "native" compiler was used.

An up-to-date Xcode and outdated command line tools would be a valid explanation for this situation.

comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Henry, can you check the output of "clang -v" on the 10.8 buildbot builder? According to XcodeVersionInfo#OSX10.8 we want it to be "Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)". If it's less, install the Xcode command line tools. To do so, open Xcode.app, go to the Preferences window, to the Downloads tab, and there should be an option to install or update the command line tools. If not, from the Apple Developer downloads page (ADC login required), you can download and install "Command Line Tools (OS X Mountain Lion) - April 2014".

comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

It should be updated now, according to Henry:

It was showing 4.1 so I updated the command line tools and it is now showing 5.1 clang-503.0.40.

Let me know if you need me to do anything else.

comment:5 Changed 10 years ago by mojca (Mojca Miklavec)

Thank you. The buildbot now says:

DEBUG: compiler clang 503.0.40 not blacklisted because it doesn't match { clang <= 318.0.61 }

which is the expected behaviour.

Note: See TracTickets for help on using tickets.