[MacPorts] #29173: ld64 should symlink rather than copy ld and rebase on darwin > 10

MacPorts noreply at macports.org
Sun Apr 17 09:47:19 PDT 2011


#29173: ld64 should symlink rather than copy ld and rebase on darwin > 10
--------------------------------------+-------------------------------------
 Reporter:  howarth@…                 |       Owner:  mfeiri@…           
     Type:  defect                    |      Status:  assigned           
 Priority:  Normal                    |   Milestone:                     
Component:  ports                     |     Version:  1.9.2              
 Keywords:                            |        Port:  ld64               
--------------------------------------+-------------------------------------

Comment(by mfeiri@…):

 Interesting thought about assembler desynchronisation... Clang has its own
 internal assembler these days, so I didnt think about this issue. I really
 really want to _reduce_ reliance on Xcode but I dont want to reopen the
 entire (od)cctools can of worms either. I do admit that, now that the
 symlink method allows us to use our own libLTO.dylib, it seems tempting to
 use the symlink method exclusively. I'll have to think about that.

 One option would be to support all three combinations (Xcode ld using
 Xcode libLTO, Xcode ld using MacPorts libLTO, MacPorts ld using MacPorts
 libLTO) by installing our own ld64 as "ld-mp" and setting up a symlink to
 Xcode's ld named "ld-mp-xc". The regular unmodified "ld" would continue to
 be accessible as usual. But that seems rather clumsy.

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


More information about the macports-tickets mailing list