[MacPorts] #46599: clang-3.6 @3.6-r226372_0 fails building on 10.6.8

[MacPorts]

#46599: clang-3.6 @3.6-r226372_0 fails building on 10.6.8
-------------------------+------------------------
  Reporter:  braumann@…  |      Owner:  jeremyhu@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.3
Resolution:              |   Keywords:
      Port:  clang-3.6   |
-------------------------+------------------------

Comment (by braumann@…):

 > My Leopard VM built it ok.

 I guess you are talking about Leopard on Intel. Since both 3.5 and 3.6
 (and probably upcoming 3.7) in turn require 3.4 for building, the latter
 should work productively. After I successfully had build 3.4 on Leopard
 (PPC) my basic "Hello, world" one liner test failed (last clang version it
 was working was 3.1):

 {{{
 $ printf '#include<stdio.h> \n int main(void) {fprintf(stderr,"Hello,
 world\\n");}' | clang-mp-3.4 -arch ppc -xc -o out.exe - && ./out.exe
 clang(39479) malloc: *** error for object 0xa02a6708: Non-aligned pointer
 being freed
 *** set a breakpoint in malloc_error_break to debug
 ...
 <dozens of such "Non-aligned pointer being freed" messages>
 ...
 ld: absolute address to symbol ___stderrp in a different linkage unit not
 supported in _main from
 /var/folders/fH/fHv2DgyLHvS8wcc5wmXwHU+++TM/-Tmp-/--855242.o
 collect2: ld returned 1 exit status
 clang: error: linker (via gcc) command failed with exit code 1 (use -v to
 see invocation)
 }}}

 As I have read somewhere that PPC support has much improved in 3.6 (I
 think since the llvm people now have started focusing again on PPC), I
 wonder how 3.6 can be built on PPC, if it relies on 3.4, which is not
 usable on PPC. 3.4 itself only requires apple gcc 4.2, I think. For the
 moment I better do not open a new ticket for the 3.4 problems on PPC, ok?

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