Warning: All compilers are either blacklisted or unavailable

[Marcus Calhoun-Lopez]

The Qt compiler is set using files in the mkspecs directory (macs-clang or macx-clang-32).
Clang is the only compiler currently supported (http://doc.qt.io/qt-5/supported-platforms.html <http://doc.qt.io/qt-5/supported-platforms.html>),
which is the reason for compiler.whitelist clang.

In the same configuration files, C++11 support is achieved via -std=c++11 and -stdlib=libc++.
The cxx11 PortGroup was added in an effort to ensure that these flags would work.

While Apple OS X 10.7 "Lion", Cocoa (64-bit) is not a “reference configuration,” it is supposed to “work well.”

Does blacklisting clang < 500 in the  cxx11 PortGroup completely preclude 10.7?

-Marcus


> On Dec 2, 2015, at 11:13 AM, Joshua Root <jmr at macports.org> wrote:
> 
> On 2015-12-3 04:05 , Mojca Miklavec wrote:
>> Hi,
>> 
>> When upgrading Qt5 I'm greeted with:
>> 
>> --->  qt5-mac is replaced by qt5
>> Warning: All compilers are either blacklisted or unavailable;
>> defaulting to first fallback option
>> 
>> I guess this is because of the cxx11 PortGroup, even though I'm not 100% sure.
>> 
>> But the main question is: why are all compilers blacklisted or rather:
>> can something be done to have some compiler in the fallback that would
>> work (like mp-clang-3.4)? Lion's clang (425) usually works, even
>> though there are some problems with it (not all C++11 code works).
> 
> The qt5 portgroup sets 'compiler.whitelist clang'.
> 
> - Josh
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20151202/f5100c92/attachment.html>