[MacPorts] #52131: cctools, ld64: Removing +llvm37 variant pulls in +llvm34 instead and toolchain becomes unstable on 10.6

[MacPorts]

#52131: cctools, ld64: Removing +llvm37 variant pulls in +llvm34 instead and
toolchain becomes unstable on 10.6
-------------------------------------+-------------------------
  Reporter:  kenneth.f.cunningham@…  |      Owner:  jeremyhu@…
      Type:  defect                  |     Status:  assigned
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:  2.3.4
Resolution:                          |   Keywords:  snowleopard
      Port:  cctools ld64            |
-------------------------------------+-------------------------

Comment (by kenneth.f.cunningham@…):

 >I understand why llvm-3.4 would be pulled in, but why was clang-3.4? That
 doesn't make sense.

 You are correct - it was just llvm-3.4. Up to now, I have thought of them
 as an inseparable intertwined versioned pair, but I can see over your last
 several posts they are actually separate entities.

 here's the log of exactly what happened during the upgrade process:

 {{{

 --->  Dependencies to be installed: llvm-3.4
 --->  Activating llvm-3.4 @3.4.2_11
 --->  Fetching distfiles for ld64-latest
 --->  Verifying checksums for ld64-latest
 --->  Extracting ld64-latest
 --->  Applying patches to ld64-latest
 --->  Configuring ld64-latest
 --->  Building ld64-latest
 --->  Staging ld64-latest into destroot
 --->  Installing ld64-latest @264.3.102_2+llvm34
 --->  Computing dependencies for ld64-latest
 --->  Deactivating ld64-latest @264.3.102_1+llvm37
 --->  Activating ld64-latest @264.3.102_2+llvm34

 }}}

 then I checked the following and and found the +llvm34 option installed:

 {{{

 $ port -v installed ld64*
 The following ports are currently installed:
  ld64 @2_0-ld64_127-ld64_136-ld64_236-ld64_97 (active) platform='darwin
 10' archs='x86_64'
  ld64 @2_0+ld64_136 platform='darwin 10' archs='x86_64'
  ld64-136 @136_5+llvm34 platform='darwin 10' archs='x86_64'
  ld64-136 @136_5+llvm37-llvm34 (active) platform='darwin 10'
 archs='x86_64'
  ld64-latest @264.3.102_1+llvm37 platform='darwin 10' archs='x86_64'
  ld64-latest @264.3.102_2+llvm34 (active) platform='darwin 10'
 archs='x86_64'

 }}}

 In retrospect, perhaps I should have just left everything as it was right
 at that point, BUT thinking that was very wrong, I tried to reactivate the
 +llvm37 variant.

 {{{

 sudo port activate ld64-latest @264.3.102_1+llvm37

 $ sudo port activate ld64-latest @264.3.102_1+llvm37
 --->  Computing dependencies for ld64-latest
 --->  Deactivating ld64-latest @264.3.102_2+llvm34
 --->  Activating ld64-latest @264.3.102_1+llvm37

 }}}

 then rechecked:

 {{{

 $ port -v installed ld64*
 The following ports are currently installed:
  ld64 @2_0-ld64_127-ld64_136-ld64_236-ld64_97 (active) platform='darwin
 10' archs='x86_64'
  ld64 @2_0+ld64_136 platform='darwin 10' archs='x86_64'
  ld64-136 @136_5+llvm34 platform='darwin 10' archs='x86_64'
  ld64-136 @136_5+llvm37-llvm34 (active) platform='darwin 10'
 archs='x86_64'
  ld64-latest @264.3.102_1+llvm37 (active) platform='darwin 10'
 archs='x86_64'
  ld64-latest @264.3.102_2+llvm34 platform='darwin 10' archs='x86_64'
 }}}

 and thought that looked right to me, but segfaulted.

 So I tried this:

 {{{

 $ sudo port upgrade --enforce-variants ld64-latest +llmv37 -llvm34
 Error: Your platform cannot be configured without LTO support in ld64.
 Please enable one of the llvmXX variants, and try again.
 }}}

 and then -- after looking around in the portfile long enough to see the
 +llvm37 variant gone -- decided to start over with +llvm38 -- deleted all
 traces of clang*, llvm*, ld64*, and cctools*, and started over with
 success in the end.

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