On Dec 9, 2013, at 10:20, Markus W. Weißmann <[email protected]> wrote:

> On 9. Dec 2013, at 17:15 , Ryan Schmidt <[email protected]> wrote:
> 
>> On Dec 9, 2013, at 07:56, [email protected] wrote:
>> 
>>> Revision
>>> 114471
>>> Author
>>> [email protected]
>>> Date
>>> 2013-12-09 05:56:39 -0800 (Mon, 09 Dec 2013)
>>> Log Message
>>> 
>>> botan: use configure.compiler
>>> Modified Paths
>>> 
>>>     • trunk/dports/security/botan/Portfile
>>> Diff
>>> 
>>> Modified: trunk/dports/security/botan/Portfile (114470 => 114471)
>>> 
>>> --- trunk/dports/security/botan/Portfile    2013-12-09 13:45:41 UTC (rev 
>>> 114470)
>>> +++ trunk/dports/security/botan/Portfile    2013-12-09 13:56:39 UTC (rev 
>>> 114471)
>>> 
>>> @@ -27,7 +27,7 @@
>>> 
>>> worksrcdir          Botan-${version}
>>> 
>>> 
>>> 
>>> configure.cmd       ./configure.py
>>> 
>>> -configure.args      --docdir=share/doc --cc=clang --with-openssl 
>>> --with-zlib --with-bzip2
>>> 
>>> +configure.args      --docdir=share/doc --cc=${configure.compiler} 
>>> --with-openssl --with-zlib --with-bzip2
>> 
>> configure.compiler is the MacPorts name for the compiler, which is not 
>> necessarily the same as the name of the executable to run; for that, use 
>> configure.cc.
>> 
>> For example, when configure.compiler is "macports-clang-3.3", configure.cc 
>> is "/opt/local/bin/clang-mp-3.3”.
> 
> Here the “—cc=“ option expects the name of the "compiler suite” -- not the 
> path of the executable of the C or C++ compiler.

Oh. But botan doesn’t know MacPorts compiler names:

$ port -dn build botan configure.compiler=macports-clang-3.3

ends with:

  ERROR: Unknown compiler "macports-clang-3.3"; available options: bcc clang 
compaq ekopath gcc hpcc icc kai mipspro msvc open64 pgi sgipro64 sunstudio xlc

The only one of those that’s routinely used in MacPorts is “clang”. It will 
fail on Xcode earlier than 4.2 where configure.compiler may be "llvm-gcc-4.2", 
"gcc-4.2", or "gcc-4.0".

It looks like they also have the option “--cc-bin” which may be better suited.


_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to