[MacPorts] #47929: llvm-gcc42 @2336.11_2 fails building on 10.6.8

[MacPorts]

#47929: llvm-gcc42 @2336.11_2 fails building on 10.6.8
-------------------------+--------------------------------
  Reporter:  braumann@…  |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.3
Resolution:              |   Keywords:
      Port:  llvm-gcc42  |
-------------------------+--------------------------------
Changes (by ryandesign@…):

 * keywords:  Symbol not found: _strncmp =>
 * cc: ryandesign@… (added)


Comment:

 Replying to [ticket:47929 braumann@…]:
 > While updating {{{llvm-gcc42}}} from {{{2336.11_1}}} to {{{2336.11_2}}}
 on 10.6.8 I was surprised to run into trouble like {{{dyld: lazy symbol
 binding failed: Symbol not found: _strncmp}}}.

 Hmm. Yesterday's update of llvm-gcc42 was done for the benefit of
 Yosemite, on which llvm-gcc42 couldn't be built until now. It's certainly
 possible this has introduced problems for earlier platforms, though this
 was not intended.

 > BTW, I am wondering that {{{llvm-gcc42}}} itself is being automatically
 selected for building.

 Well, the llvm-gcc42 port will not build using a compiler installed by an
 already-installed llvm-gcc42 port. What you're seeing in the log is that
 the llvm-gcc42 port is being compiled using the version of the llvm-gcc42
 compiler that came with Xcode.

 Theoretically, that should work. However, on my Snow Leopard system, Xcode
 gcc42 is used, not llvm-gcc42, and I don't see anything in the llvm-gcc42
 portfile that would explain why Xcode llvm-gcc42 was selected instead on
 your system.

 Do you really need MacPorts llvm-gcc42? Is the version provided by Xcode
 not sufficient for your needs? It is true that the MacPorts version is
 ever so slightly newer than the version provided by Xcode, but there are
 only a few small differences.

 > Below is the most relevant excerpt. I am hesitating to directly report
 to [http://developer.apple.com/bugreporter]

 You're probably right not to report this to Apple; they've moved on from
 llvm-gcc. We keep it around mainly for the benefit of very old software
 that has not yet been fixed to compile properly with clang on newer
 systems.

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