[110463] trunk/dports/mail/mailsync/Portfile

Ryan Schmidt ryandesign at macports.org
Sat Aug 31 16:54:11 PDT 2013


On Aug 31, 2013, at 03:00, jeremyhu at macports.org wrote:

> Revision: 110463
>          https://trac.macports.org/changeset/110463
> Author:   jeremyhu at macports.org
> Date:     2013-08-31 01:00:38 -0700 (Sat, 31 Aug 2013)
> Log Message:
> -----------
> mailsync: Remove clang blacklist.  It was incorrectly added.
> 
> Modified Paths:
> --------------
>    trunk/dports/mail/mailsync/Portfile

Blacklisting clang fixed the error reported in #39202. By removing the blacklist you've brought back the problem, for users with affected versions of clang.

I can reproduce the build failure using macports-clang-2.9 and macports-clang-3.0:

checking if c-client works without -fno-operator-names in c++... no
checking if adding -fno-operator-names helps... no
configure: error: a working c-client installation is required for building mailsync

The config.log says:

In file included from conftest.cc:33:
/opt/local/include/c-client/c-client.h:36:9: error: C++ operator 'and' cannot be used as a macro name
#define and cclientAnd          /* C99 doesn't realize that ISO 646 is dead */
        ^
/opt/local/include/c-client/c-client.h:37:9: error: C++ operator 'or' cannot be used as a macro name
#define or cclientOr
        ^
/opt/local/include/c-client/c-client.h:38:9: error: C++ operator 'not' cannot be used as a macro name
#define not cclientNot
        ^

macports-clang-3.1 and later don't cause this error so we don't need to blacklist them.

#39202 was filed by a user on Snow Leopard and the compiler chosen was clang, which means it was the old version of clang in Xcode 4.2.


More information about the macports-dev mailing list