[MacPorts] #38410: Lion buildbot disconnected while building textmate2 @2.0.9395 (was: Lion buildbot disconnected)

MacPorts noreply at macports.org
Sun Mar 17 23:44:02 PDT 2013


#38410: Lion buildbot disconnected while building textmate2 @2.0.9395
-----------------------------+-------------------------
  Reporter:  ryandesign@…    |      Owner:  wsiegrist@…
      Type:  defect          |     Status:  reopened
  Priority:  Normal          |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:  textmate2       |
-----------------------------+-------------------------
Changes (by ryandesign@…):

 * status:  closed => reopened
 * cc: cal@… (added)
 * resolution:  fixed =>
 * port:   => textmate2


Comment:

 It happened again, at exactly the same place building the same port
 textmate2 @2.0.9395 (step "![155/157]"). Has the Lion buildbot experienced
 a kernel panic or what is the symptom?

 I tried building textmate2 on my Lion machine with Xcode 4.3.3 and got:
 {{{
 Error: On Mac OS X 10.7, textmate2 2.0.9395 requires Xcode 4.4 or later
 but you have Xcode 4.3.3.
 Error: See http://guide.macports.org/chunked/installing.xcode.html for
 download links.
 Error: org.macports.extract for port textmate2 returned: incompatible
 Xcode version
 }}}

 This is because of this line in the portfile:
 {{{
 minimum_xcodeversions   {11 4.4}
 }}}

 This was added in r98375 to fix #36443 because textmate2 requires the 10.8
 SDK even on 10.7.

 If I remove the `minimum_xcodeversions` line, I get:
 {{{
 /usr/bin/clang is too old to build this project.

 Please see README.md for build instructions.
 }}}

 I remember that awhile ago the Lion buildbot was using Xcode 4.3.3. It
 seems it has been updated since then (maybe when it was converted from a
 standalone server to a virtual machine?) but perhaps the command line
 tools were not updated and are thus still at the version of Xcode 4.3.3?
 Bill, what does running `clang -v` on the Lion buildbot say? What about
 `xcodebuild -version`?

 The port should probably use the compiler_blacklist_versions portgroup to
 blacklist old clangs that are known not to work, so that any users who
 have updated Xcode but not its command line tools (which is quite a common
 occurrence) do not run into problems, or at least encounter a friendlier
 or earlier error message.

 I will also test on a Mountain Lion Mac that still has Xcode 4.5.2 and its
 `Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM
 3.1svn)` but it will take some time to build boost first.

-- 
Ticket URL: <https://trac.macports.org/ticket/38410#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list