Fortran recipe

[Jeremy Huddleston Sequoia]

On Aug 25, 2013, at 11:29, Ryan Schmidt <ryandesign at macports.org> wrote:

> 
> On Aug 25, 2013, at 12:56, Chris Jones wrote:
> 
>> Its not clear to me if we also need to remove the variants that build with Macports clang. As I understand things these aren't affected by the c++ runtime issues ? These variants are still useful, for instance if the users wants to use the cocoa graphical backend, as these only works when built with clang, so on systems that don't use this as a default compiler, its convenient to have the clang variants as a fall back.
> 
> Are there any drawbacks to using clang? If not, maybe you should blacklist those compilers that won't build the cocoa backend. That way the cocoa backend will always be available.

I suggest that your +cocoa variants use "compiler.whitelist macports-clang-3.2 macports-clang-3.1" to force one of those compilers.  Can you explain why 3.3 and Apple clang don't work?

For Fortran, you should just set compiler.fc, etc.  This will ensure that you have a fortran compiler and are using a C++ compiler that uses the expected C++ runtime.

--Jeremy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20130825/0ff3d053/attachment.p7s>