#39585: Today's clang-3.3 is broken --------------------------------+------------------------ Reporter: feliks.kluzniak@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: clang-3.3 | --------------------------------+------------------------ Changes (by ryandesign@…): * cc: feliks.kluzniak@… (removed) * owner: macports-tickets@… => jeremyhu@… -- Ticket URL: <https://trac.macports.org/ticket/39585#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#39585: Today's clang-3.3 is broken --------------------------------+------------------------ Reporter: feliks.kluzniak@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: clang-3.3 | --------------------------------+------------------------ Comment (by feliks.kluzniak@…): Replying to [comment:3 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. :-) ) -- Ticket URL: <https://trac.macports.org/ticket/39585#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#39585: Today's clang-3.3 is broken --------------------------------+------------------------ Reporter: feliks.kluzniak@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: clang-3.3 | --------------------------------+------------------------ Comment (by jeremyhu@…): upgrading should preserve variants … did that not happen in your case? clang and llvm need to match on whether or not they have +assertions -- Ticket URL: <https://trac.macports.org/ticket/39585#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#39585: Today's clang-3.3 is broken --------------------------------+------------------------ Reporter: feliks.kluzniak@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: clang-3.3 | --------------------------------+------------------------ Comment (by feliks.kluzniak@…): Replying to [comment:7 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! -- Ticket URL: <https://trac.macports.org/ticket/39585#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X