[MacPorts] #34413: circular dependency between cctools and llvm-2.9

MacPorts noreply at macports.org
Sun May 20 15:52:28 PDT 2012


#34413: circular dependency between cctools and llvm-2.9
--------------------------------------+-------------------------------------
  Reporter:  ryandesign@…             |       Owner:  jeremyhu@…           
      Type:  defect                   |      Status:  closed               
  Priority:  Normal                   |   Milestone:                       
 Component:  ports                    |     Version:  2.0.4                
Resolution:  fixed                    |    Keywords:  tiger                
      Port:  cctools, llvm-2.9        |  
--------------------------------------+-------------------------------------

Comment(by ultrajoe@…):

 Replying to [comment:10 jeremyhu@…]:
 > Replying to [comment:9 ultrajoe@…]:
 > > Replying to [comment:8 ultrajoe@…]:
 > > > I '''did''' find out that the initial install/upgrade of ld64 must
 be the {{{-llvm29}}} "variant," lest the lack of llvm anywhere on Tiger
 causes an issue. (I might be done by now had I known that.)
 >
 > Right, this is why on Tiger, ld64 does not set +llvmXX as a default
 variant and includes this comment:
 > {{{
 > # We don't set llvmXX as the default variant on Tiger because it would
 introduce a
 > # dependency cycle as llvm requires apple-gcc42 and ld64 to build
 correctly.  Users
 > # wanting LTO support in ld64 on Tiger can install the +llvm variant
 after llvm
 > # has been installed.
 > }}}
 >
 > > Ergo {{{-llvm29}}} = {{{+bootstrap}}}, to get back to the original
 problem report.
 >
 > Huh?

 I'm saying the same thing. When I tried reloading ld64, per your
 instructions in [comment:6 comment 6], it bailed out because it couldn't
 find llvm-2.9. I see the code & comment in the Portfile, but my
 configuration didn't seem to care. I had to {{{port install ld64
 -llvm29}}} (i.e., forcibly disable +llvm29) to get it to build on Tiger
 PPC. That sounded like the {{{+bootstrap}}} idea you had in [comment:2
 comment 2].

 > Anyways, r93318

 After fighting the 2.10 mess (#34463) and this, perhaps I should just
 backtrack to the previously installed & activated versions of everything
 and wait a few weeks or months or more to risk any further upgrades on my
 old Sawtooth G4.

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


More information about the macports-tickets mailing list