how to replace llvm-3.2 with llvm-3.3?

Christopher David Ramos m74z00219 at gmail.com
Thu Jun 26 16:01:20 PDT 2014


EDIT: This is me replying to all :) Thanks again, Ryan!

Thank you very much for your help, Ryan. You were concise and very clear.

I understand now how to obtain port maintainer contact info from the
command line.

It seems to me that general procedure is as follows:

If I need a newer version of a port, yet am unable to uninstall the old
version, I should first install the newer versions of said port's
dependencies. Then I can uninstall the older versions of those
dependencies and the older version of the port of interest.

I think I'm still "missing" sometimes as I had assumed that this sort of
maintenance work was handled by macports whenever I did a "sudo port
upgrade outdated".

If I'm mistaken, please disabuse me of any nonsense.

Oh, and just to be abundantly clear, your instructions worked pefectly.



Sincerely,




On 6/25/14, 8:56 PM, Ryan Schmidt wrote:
> On Jun 25, 2014, at 6:39 PM, Christopher David Ramos write:
>
>> While I know the maintainer is jeremyhu*, I have so far been
>> unsuccessful in determining how to contact him directly.
> Sending him an email should work. His email address is part of the output produced by running the command "port info llvm-3.2".
>
>
>> I am running MacPorts 2.3.0 on Mavericks 10.9.3. I have been unable to
>> build llvm-3.2; however, today I figured out that it is no longer
>> supported.
> As far as I know, llvm-3.2 should still build on Mavericks, though it is not supported on Yosemite at this time. However, newer versions of llvm are available, so you should probably use those, as you're trying to do.
>
>
>> OK. So, that means I'd like to remove llvm-3.2 and replace it
>> with llvm-3.3; however, I cannot remove llvm-3.3 due to dependencies.
> Which dependencies? To find out, run:
>
> port installed depends:llvm-3.2
>
>
>> Here's my question: what is the proper procedure to replace llvm-3.2
>> with llvm-3.3 whilst keeping all dependencies functioning properly?
> Two common ports that depend on llvm are cctools and ld64. They have variants for selecting which version of llvm you want to use. They default changes, as newer version of llvm are released, however once you install the port, MacPorts ensures the same variant continues to get used. So it could be that you initially installed cctools and ld64 back when llvm32 was its default variant. You could fix that by reinstalling ld64 with its now-current llvm34 default variant, and then doing the same for cctools, by running:
>
> sudo port install ld64
> sudo port install cctools
>
> Or if you prefer to use the older llvm-3.3 instead of the newer llvm-3.4, you could:
>
> sudo port install ld64 +llvm33
> sudo port install cctools +llvm33
>
> Assuming no other installed ports still depend on llvm-3.2, you should then be able to uninstall the old ld64 and cctools ports and llvm-3.2 itself.
>

-- 
Chris David Ramos



More information about the macports-users mailing list