[MacPorts] #36026: ld64 sometimes builds wrong which causes other software to fail to build

[MacPorts]

#36026: ld64 sometimes builds wrong which causes other software to fail to build
-------------------------+------------------------
  Reporter:  jwhowse4@…  |      Owner:  jeremyhu@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.1.2
Resolution:              |   Keywords:
      Port:  ld64        |
-------------------------+------------------------

Comment (by jwhowse4@…):

 Replying to [comment:75 jeremyhu@…]:
 > I have the macports-tst1 and macports-tst2 tarballs from your config.
 I'm going to extract them into /opt on my Lion machine with XCode 4.5 and
 do:
 >
 > {{{
 > PATH=/opt/macports-tst1/bin:$PATH
 > sudo port -v install llvm-3.1
 > sudo port -v install ld64 +llvm31
 >
 > PATH=/opt/macports-tst2/bin:$PATH
 > sudo port -v install llvm-3.1
 > sudo port -v install ld64 +llvm31
 > }}}
 >
 > You're expecting that one of these will produce a working ld and one
 will not.  By working / not working, we mean that using it to replace
 /opt/local/bin/ld will cause x86_64 code to link (or not link) when using
 one of MacPorts' gcc4X compilers.
 >
 > Is that correct?

 Actually as I indicated in my initial reply, under XCode 4.5.0 neither of
 these examples gives me a working linker.  In fact I have tried some other
 package orderings and so far I can not find an ordering which gives a
 working linker with XCode 4.5.0.  Strangely every ordering gives me a
 different linker, but none of them work.

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