Fortran recipe

Ryan Schmidt ryandesign at macports.org
Sun Aug 25 12:30:33 PDT 2013


On Aug 25, 2013, at 14:23, Chris Jones wrote:

> On 25 Aug 2013, at 8:17pm, Ryan Schmidt wrote:
> 
>> On Aug 25, 2013, at 14:15, Chris Jones wrote:
>> 
>>> So now I have
>>> 
>>>>  PortGroup compiler_blacklist_versions 1.0
>>>>  # Force a compatible clang compiler
>>>>  compiler.blacklist-append {clang < 425}
>>>>  compiler.fallback-append macports-clang-3.2 macports-clang-3.1
>>> 
>>> To make this work though, I also need to black list any compiler that isn't clang, so on systems where the default system compiler isn't clang, it will fallback to the macports-clang, no ? whats the string to add to the blacklist list for this ?
>> 
>> compiler.blacklist-append apple-gcc-4.0 apple-gcc-4.2 gcc-3.3 gcc-4.0 gcc-4.2 llvm-gcc-4.2 macports-gcc-4.2 macports-gcc-4.3 macports-gcc-4.4 macports-gcc-4.5 macports-gcc-4.6 macports-gcc-4.7 macports-gcc-4.8 macports-gcc-4.9 macports-llvm-gcc-4.2
>> 
> 
> Ah thanks. I was hoping there was a way to wild card that somehow ( so to match say *gcc*) to avoid a long list like that ?

I forgot: yes, wildcard support was added to compiler.blacklist 5 months ago:

https://trac.macports.org/changeset/104174

"portconfigure.tcl: Allow globs in compiler.blacklist. This allows things like `compiler.blacklist *gcc*`. Any pattern accepted by Tcl's "string match" is valid."

I hadn't been using that because we had not released a new version of MacPorts base containing that fix. But MacPorts 2.2 does include that fix, so now we can use it.


Also, add macports-clang-2.9 and macports-clang-3.0 to the list, if those won't work for root.



More information about the macports-dev mailing list