#39202 closed defect (fixed)
mailsync @5.2.1: configure fails with clang
Reported by: | posita (Matt Bogosian) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: | mailsync |
Description
Error in log (complete build and config logs attached):
:info:configure checking if c-client works without -fno-operator-names in c++... no :info:configure checking if adding -fno-operator-names helps... no :info:configure configure: error: a working c-client installation is required for building mailsync :info:configure Command failed: cd "/__PATH__/var/macports/build/___PATH___var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_mailsync/mailsync/work/mailsync-5.2.1" && ./configure --prefix=/__PATH__ --with-c-client=/__PATH__ --with-krb5=/__PATH__ --with-openssl=/__PATH__ --mandir=/__PATH__/share/man :info:configure Exit code: 1 :error:configure org.macports.configure for port mailsync returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for mailsync: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port mailsync for details: /__PATH__/var/macports/logs/___PATH___var_macports_sources_rsync.macports.org_release_tarballs_ports_mail_mailsync/mailsync/main.log
Attachments (2)
Change History (9)
Changed 11 years ago by posita (Matt Bogosian)
comment:1 Changed 11 years ago by posita (Matt Bogosian)
Errors from config:
In file included from conftest.cc:33: /__PATH__/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 */ ^ /__PATH__/include/c-client/c-client.h:37:9: error: C++ operator 'or' cannot be used as a macro name #define or cclientOr ^ /__PATH__/include/c-client/c-client.h:38:9: error: C++ operator 'not' cannot be used as a macro name #define not cclientNot ^ In file included from conftest.cc:33: In file included from /__PATH__/include/c-client/c-client.h:41: /__PATH__/include/c-client/mail.h:940:13: error: expected member name or ';' after declaration specifiers SEARCHOR *or; /* or'ed in programs */ ~~~~~~~~ ^ /__PATH__/include/c-client/mail.h:941:18: error: expected member name or ';' after declaration specifiers SEARCHPGMLIST *not; /* and'ed not program */ ~~~~~~~~~~~~~ ^ 5 errors generated.
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
Can you try using LLVM-GCC?
% sudo port clean mailsync % sudo port install mailsync configure.compiler=llvm-gcc-4.2
comment:3 follow-up: 4 Changed 11 years ago by posita (Matt Bogosian)
That worked.
Is it possible to incorporate this as part of the port? Are there such things as conditional build dependencies (i.e., if platform X, build tools Y, depend on llvm-gcc-4.2, etc.)? My apologies for my ignorance....
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Summary: | mailsync @5.2.1 can't find c-client → mailsync @5.2.1: configure fails with clang |
MacPorts maintains lists of compilers that it prefers to use, based on Xcode version.
Ideally someone would patch the source to build correctly with Clang, but I have neither the time nor interest to do so, especially with such an old piece of software. I just blacklisted all Clang values in r106366.
comment:5 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
That error seems to have nothing to do with clang... reverted in r110463
You've got a ton of __PATH__
tokens in configure for some reason...
Works for me, so just removing the blacklisting.
comment:6 Changed 11 years ago by posita (Matt Bogosian)
The __PATH__
tokens are from a search-and-replace I did on the logs. I was trying to highlight that MacPorts was installed in a non-standard place. If I didn't already mention it, my installation is also a user installation (e.g., installed in /home/[USER]/.macports or something similar).
comment:7 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Ah. Sorry for not understanding that. I've verified that the issue exists with 2.9 and 3.0, so blacklisting those and < 400 in r110553
build log