[MacPorts] #42112: clang-3.4 build failure with gcc-4.2 on OS X 10.6.8

[MacPorts]

#42112: clang-3.4 build failure with gcc-4.2 on OS X 10.6.8
--------------------------+-------------------------
  Reporter:  rjvbertin@…  |      Owner:  jeremyhu@…
      Type:  defect       |     Status:  closed
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.2.1
Resolution:  worksforme   |   Keywords:  snowleopard
      Port:  clang-3.4    |
--------------------------+-------------------------

Comment (by jeremyhu@…):

 Replying to [comment:12 rjvbertin@…]:
 > Update: I've never managed to get clang-3.4 to build with apple's
 gcc-4.2, not even after relaunching the build command multiple times in a
 row.

 How many times did you try?  I think I got it after 5-6.

 > As I had a working version, I let it slip, but I have to come back to
 that.
 >
 > The latest llvm-3.4_1 update caused clang-3.4 to crash during
 compilation. As llvm-3.4 had been upgraded with upgrade outdated, I
 figured I'd reinstall it, ensuring that I'd be building with gcc-4.7 .

 How did it crash?  Do you have crash reporter logs?

 > That worked, but now clang-3.4 will not rebuild, not even with macports-
 gcc-4.8 as it did before.

 This issue looks like a dependencies issue in the Makefiles for
 compiler_rt and does not seem at all related to what compiler is chosen.

 > The failure is the same as I observed with gcc-4.2. Moving into the
 build directory and invoking make by hand, I see

 Yes, that is what I'd expect (ie, that's this bug).

 > Why is clang trying to build for armv7 - I never asked for that! Is
 there a way to deactivate support for that (and other cross-compiling) as
 I won't ever be using such features?

 Do you have the +arm_runtime variant selected?

 > Let me know if I should open a new ticket for this.

 No, this is the right ticket.

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