[MacPorts] #30731: arm-none-eabi-binutils doesn't compile with newest Xcode (4D151a)

[MacPorts]

#30731: arm-none-eabi-binutils doesn't compile with newest Xcode (4D151a)
-------------------------------------+--------------------------------------
  Reporter:  mail@…                  |       Owner:  macports-tickets@…                   
      Type:  defect                  |      Status:  reopened                             
  Priority:  Normal                  |   Milestone:                                       
 Component:  ports                   |     Version:  2.0.1                                
Resolution:                          |    Keywords:  haspatch                             
      Port:  arm-none-eabi-binutils  |  
-------------------------------------+--------------------------------------

Comment(by adfernandes@…):

 Replying to [comment:5 ryandesign@…]:
 > r87830 changes the compiler unconditionally to llvm-gcc-4.2. Did you not
 read comment:1 above which reminds us that llvm-gcc-4.2 is not available
 in earlier OS X versions' Xcodes? Please see PortfileRecipes#compiler for
 the way in which we usually want to select llvm-gcc-4.2 when clang would
 otherwise have been selected. Please see also comment:2 which suggests an
 alternative that may allow us to use clang after all.

 Whups. Added the "use llvm-gcc if clang" in r87840. Of course, I doubt
 that that solves the problem.

 The `PortfileRecipes` page doesn't say how to solve this problem, if
 indeed it can be solved. The `gnu binutils` assume, to a large extent, the
 gcc compiler suite, and a fairly recent one. The "compiler fallback" stuff
 is not particularly useful, methinks, if it can't be tested (which, for
 most of us, it can't be).

 Maybe a better way to go about it is, for every port, a list of
 "blacklisted" compilers - "known not to work with pre-gcc-4.1" or "known
 not to work with pre-clang-3"?

-- 
Ticket URL: <https://trac.macports.org/ticket/30731#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS