[MacPorts] #64600: Is there any special reason why llvm-3.5 is deprecated while llvm-3.3 and llvm-3.4 are kept?

[MacPorts]

#64600: Is there any special reason why llvm-3.5 is deprecated while llvm-3.3 and
llvm-3.4 are kept?
-------------------------------------------+-------------------------------
  Reporter:  barracuda156                  |      Owner:  (none)
      Type:  update                        |     Status:  new
  Priority:  Normal                        |  Milestone:
 Component:  ports                         |    Version:  2.7.1
Resolution:                                |   Keywords:  powerpc, leopard,
      Port:  llvm-3.3, llvm-3.4, llvm-3.5  |  llvm
-------------------------------------------+-------------------------------

Comment (by barracuda156):

 Replying to [comment:4 kencu]:
 > I never tried building ld64-127 against llvm-3.7 on PPC, I think.

 Got it. I will try that perhaps, since I get linker failures with some
 configurations which I cannot fix directly (so trying another combo might
 possibly help).

 > I have had llvm/clang/libcxx 5.0 running on my 10.5 PPC system since
 about 2018, but it generates ABI-broken code so never moved it into MP.

 I have been just re-reading your post on it:
 https://trac.macports.org/ticket/53184
 Will clang-3.x work with `libstdc++` or I should switch it to `libc++`? If
 the second, can we link against different libs within same Macports
 installation? (And what about lib setting for llvm?)

-- 
Ticket URL: <https://trac.macports.org/ticket/64600#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS