Current best practice to select GCC compiler in Portfile

[Christopher Jones]

The best practise is not to do it, unless it is for non C++ code (C, fortran, ..), as using gcc for C++ will lead to C++ runtime issues if the binaries you produce are used with others that where produced using clang, which like it or not is now the default OS X compiler.

> On 26 Feb 2015, at 1:56pm, Artur Szostak <aszostak at partner.eso.org> wrote:
> 
> Hi,
> 
> I couldnt really find this information and I see lots of different approaches in the Portfiles.
> What is the current best practice to select the GCC compiler over the XCode clang one used by default?
> I dont care much about the exact version of the GCC compiler used, but it must be gcc rather than clang.
> 
> Kind regards.
> 
> Artur
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2030 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150226/985098b6/attachment-0001.p7s>