[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 aron.j.silverton@…):

 Replying to [comment:4 jwhowse4@…]:
 > Replying to [comment:1 jeremyhu@…]:
 > > > I then tried replacing the linker ld from the ld64 port with the
 apple linker from Xcode 4.4.1
 > >
 > > Can you please tell me *precisely* what you did here since there is
 actually a lot more room for ambiguity in that statement than you realize.
 [[br]]
 > > [[br]]
 > > What is the output of?
 > >
 > {{{
 > /path/to/ld -v
 > }}}
 > >
 > > Where /path/to/ld is the "updated" ld that you replaced.
 >
 > In the directory /opt/macports/bin (which is where I put MacPorts) I ran
 the following commands.
 >
 >
 > {{{
 > mv ld ld.macports
 > ln -s /usr/bin/ld ld
 > }}}
 >
 > Now the command /opt/macports/bin/ld -v gives
 >
 > {{{
 > @(#)PROGRAM:ld  PROJECT:ld64-133.3
 > configured to support archs: armv6 armv7 i386 x86_64
 > LTO support using: LLVM version 3.1svn, from Apple Clang 4.0 (build
 421.0.60)
 > }}}
 >
 >

 I can confirm that:

 {{{
 mv ld ld.bak
 ln -s /usr/bin/ld ld
 }}}

 Is a workaround. I can now build Macports that depend on GCC, libstdcxx,
 etc.

 I'm looking forward to a permanent fix.

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