Today's clang-3.3 is broken

[feliks.kluzniak@…]

When clang-3.3 is upgraded by importing a binary file, the check for broken links fails. This causes a rebuild of clang-3.3, which takes a lot of time. Then the check for broken links fails, which causes a rebuild ...

I have interrupted this, uninstalled clang-3.3, cleaned clang-3.3 and then tried to install it from scratch. Same results.

This is on a 2010 MacBook Pro with the current version of everything: MacOS X 10.8.4, command line tools of XCode 4.6.3, always preceding upgrade with selfupdate.

[feliks.kluzniak@…]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

What links are broken?

[feliks.kluzniak@…]

Replying to jeremyhu@…:

What links are broken?

I have no idea: this happens during the automatic checking at the end of an upgrade or install. One thing seems certain: this has to do with clang-3.3, for after uninstalling it the automatic check passes after other upgrades.

Is there any way I can get more information? A verbose option? It's not clear from the output for 'help".

(As far as MacPorts itself is concerned I am just a naive user, and most of the time a happy one. :-) )

[seanfarley (Sean Farley)]

Replying to jeremyhu@…:

What links are broken?

What he means is that the port isn't downloading the binary (I just ran into this).

feliks, the issue is that the default variants changed. You could fix this a few ways but uninstalling then installing should work.

[jeremyhu (Jeremy Huddleston Sequoia)]

upgrading should preserve variants … did that not happen in your case?

clang and llvm need to match on whether or not they have +assertions

[jeremyhu (Jeremy Huddleston Sequoia)]

Replying to feliks.kluzniak@…:

Replying to jeremyhu@…:

What links are broken?

I have no idea: this happens during the automatic checking at the end of an upgrade or install. One thing seems certain: this has to do with clang-3.3, for after uninstalling it the automatic check passes after other upgrades.

Is there any way I can get more information? A verbose option? It's not clear from the output for 'help".

Set this in /opt/local/etc/macports/macports.conf:

revupgrade_mode	report

[feliks.kluzniak@…]

Replying to jeremyhu@…:

Set this in /opt/local/etc/macports/macports.conf:

revupgrade_mode	report

I should have figured out this had something to do with the earlier upgrade of llvm-3.3. My apologies!

I got into this state:

The following versions of llvm-3.3 are currently installed:
--->      llvm-3.3 @3.3-r180025_0+assertions (active)
--->      llvm-3.3 @3.3_0+assertions

And my difficulty was

--->  Found 1 broken port(s):
     clang-3.3 @3.3 +analyzer+python27
         /opt/local/libexec/llvm-3.3/lib/libclang.dylib

Cleaning both llvm and clang and re-installing both solved the problem

Many thanks to you and Sean for your prompt and effective help!