Re: compilers PortGroup

[Mark Brethen]

It’s a local port I’m updating. The source does not have configure, so the makefile has to be patched and build environment passed.

Portfile
Description: Binary data

Mark Brethenmark.bret...@gmail.com


On Jul 17, 2022, at 6:41 PM, Ken Cunningham  wrote:Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
To work around this, you need to add -fallow-argument-mismatch to the FFLAGS inside Makefile:
Funny, that is exactly the argument that:compilers.allow_arguments_mismatch yesis supposed to add for you to fix this. Now I wonder why it doesn’t add it?What port are you trying to build again? Something fishy here, it seems.K

Re: compilers PortGroup

[Ken Cunningham]

> Error: Rank mismatch between actual argument at (1) and actual argument at 
> (2) (rank-1 and scalar)
> To work around this, you need to add -fallow-argument-mismatch to the FFLAGS 
> inside Makefile:

Funny, that is exactly the argument that:
compilers.allow_arguments_mismatch yes
is supposed to add for you to fix this. Now I wonder why it doesn’t add it?

What port are you trying to build again? Something fishy here, it seems.

K

Re: compilers PortGroup

[Mark Brethen]

Have I got this right? It seems to work:

set ver [regsub -all {[[:alpha:]]+} ${compilers.gcc_default} {}]
if { ${ver} >= 10 } {
reinplace \
"s|FFLAGS = -Wall -O2|FFLAGS = -Wall -O2 
-fallow-argument-mismatch|g" \
${worksrcpath}/src/Makefile
}


Thanks,
Mark



> On Jul 17, 2022, at 12:48 PM, Mark Brethen  wrote:
> 
> Unfortunately spooles is no longer maintained, but I found this discussion 
> online:
> 
> If you compile with GCC 10 or newer, you will get the following error, 
> originating from CalculiX:
> 
> Error: Rank mismatch between actual argument at (1) and actual argument at 
> (2) (rank-1 and scalar)
> To work around this, you need to add -fallow-argument-mismatch to the FFLAGS 
> inside Makefile:
> 
> - FFLAGS = -Wall -O3 -fopenmp $(INCLUDES)
> + FFLAGS = -Wall -O3 -fopenmp -fallow-argument-mismatch $(INCLUDES)
> 
> I’ll implement this in a patch, assuming everyone is building with >+ 10? 
> Would it hurt to patch it even if gcc <10?
> 
> Mark 
> 
> 
> 
>> On Jul 17, 2022, at 12:01 PM, Chris Jones > > wrote:
>> 
>> Ok, shame.
>> 
>> Nevertheless, this is not an issue with the compiler but the code itself. 
>> You might try discussing it with the upstream maintainers.
>> 
>> Chris
>> 
>>> On 17 Jul 2022, at 3:29 pm, Mark Brethen >> > wrote:
>>> 
>>> Hmm, 'compilers.allow_arguments_mismatch yes’ had no effect—same failure. 
>>> I looked at the compilers group and with it set, and gfortran variant is 
>>> selected, chooses ${compilers.gcc_default}. Which in my case was 
>>> gcc12—which is already installed.
>>> 
>>> Mark Brethen
>>> mark.bret...@gmail.com 
>>> 
>>> 
>>> 
 On Jul 17, 2022, at 6:15 AM, Chris Jones >>> > wrote:
 
 
 
> On 17 Jul 2022, at 1:59 am, Mark Brethen  > wrote:
> 
> I’ve tested the build with gfortran-mp-12  which fails:
> 
> :info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
> :info:build gencontelem_n2f.f:595:39:
> :info:build   184 |call 
> isortii(ialset(istartset(iset)),idummy,
> :info:build   |2
> :info:build ..
> :info:build   595 | call 
> isortii(nodef,iorder,nopes,kflag)
> :info:build   |   1
> :info:build Error: Rank mismatch between actual argument at (1) and 
> actual argument at (2) (scalar and rank-1)
> :info:build make: *** [gencontelem_n2f.o] Error 1
> 
> How is a particular value of gfortran blacklisted, in this case 
> gfortran-mp-12? 
 
 As Ken has eluded to, this is not a problem with the compiler, but an 
 issue i. The code itself made apparent by stricter checks in recent 
 compilers. You will likely run into the same with most recent versions so 
 blacklisting is not the fix here.
 
 The option Ken mentioned turns off those checks
 
 https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L782
  
 
 
 so is definitely the way forward I would think.
 
 Chris
 
> 
> Mark Brethen
> mark.bret...@gmail.com 
> 
> 
> 
>> On Jul 6, 2022, at 10:19 PM, Mark Brethen > > wrote:
>> 
>> The Spooles library is written in C language and has multi-threading 
>> subroutines.
>> 
>> Mark Brethen
>> mark.bret...@gmail.com 
>> 
>> 
>> 
>>> On Jul 6, 2022, at 5:06 PM, Joshua Root >> > wrote:
>>> 
>>> On 2022-7-7 07:40 , Mark Brethen wrote:
 The source is a combination of C and fortran, so a C-compiler with 
 fortran is needed-preferably gcc. The gcc8 build is the only one that 
 does not issue those warnings. But I have successfully run 
 verification test cases packaged with the source against gcc8, gcc9, 
 gcc11 and gfortran builds.
 The compilers PortGroup sets gfortran by default with these settings:
 compilers.choosefc cc
 compilers.setup require_fortran -g95 -clang
 But it uses clang to compile the C-code. I tried blacklisting clang 
 but then it wants to install clang-14. Choosing a gcc variant uses its 
 associated mp-gfortan compiler.
>>> 
>>> Yes, +gfortran is there to only give you a fortran compiler (because 
>>> clang doesn't have one). Is there a reason you need the C code to be 
>>> compiled with gcc?
>>> 
>>> - Josh
>>

Re: compilers PortGroup

[Mark Brethen]

Unfortunately spooles is no longer maintained, but I found this discussion 
online:

If you compile with GCC 10 or newer, you will get the following error, 
originating from CalculiX:

Error: Rank mismatch between actual argument at (1) and actual argument at (2) 
(rank-1 and scalar)
To work around this, you need to add -fallow-argument-mismatch to the FFLAGS 
inside Makefile:

- FFLAGS = -Wall -O3 -fopenmp $(INCLUDES)
+ FFLAGS = -Wall -O3 -fopenmp -fallow-argument-mismatch $(INCLUDES)

I’ll implement this in a patch, assuming everyone is building with >+ 10? Would 
it hurt to patch it even if gcc <10?

Mark 



> On Jul 17, 2022, at 12:01 PM, Chris Jones  wrote:
> 
> Ok, shame.
> 
> Nevertheless, this is not an issue with the compiler but the code itself. You 
> might try discussing it with the upstream maintainers.
> 
> Chris
> 
>> On 17 Jul 2022, at 3:29 pm, Mark Brethen  wrote:
>> 
>> Hmm, 'compilers.allow_arguments_mismatch yes’ had no effect—same failure. I 
>> looked at the compilers group and with it set, and gfortran variant is 
>> selected, chooses ${compilers.gcc_default}. Which in my case was gcc12—which 
>> is already installed.
>> 
>> Mark Brethen
>> mark.bret...@gmail.com 
>> 
>> 
>> 
>>> On Jul 17, 2022, at 6:15 AM, Chris Jones >> > wrote:
>>> 
>>> 
>>> 
 On 17 Jul 2022, at 1:59 am, Mark Brethen >>> > wrote:
 
 I’ve tested the build with gfortran-mp-12  which fails:
 
 :info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
 :info:build gencontelem_n2f.f:595:39:
 :info:build   184 |call 
 isortii(ialset(istartset(iset)),idummy,
 :info:build   |2
 :info:build ..
 :info:build   595 | call 
 isortii(nodef,iorder,nopes,kflag)
 :info:build   |   1
 :info:build Error: Rank mismatch between actual argument at (1) and actual 
 argument at (2) (scalar and rank-1)
 :info:build make: *** [gencontelem_n2f.o] Error 1
 
 How is a particular value of gfortran blacklisted, in this case 
 gfortran-mp-12? 
>>> 
>>> As Ken has eluded to, this is not a problem with the compiler, but an issue 
>>> i. The code itself made apparent by stricter checks in recent compilers. 
>>> You will likely run into the same with most recent versions so blacklisting 
>>> is not the fix here.
>>> 
>>> The option Ken mentioned turns off those checks
>>> 
>>> https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L782
>>>  
>>> 
>>> 
>>> so is definitely the way forward I would think.
>>> 
>>> Chris
>>> 
 
 Mark Brethen
 mark.bret...@gmail.com 
 
 
 
> On Jul 6, 2022, at 10:19 PM, Mark Brethen  > wrote:
> 
> The Spooles library is written in C language and has multi-threading 
> subroutines.
> 
> Mark Brethen
> mark.bret...@gmail.com 
> 
> 
> 
>> On Jul 6, 2022, at 5:06 PM, Joshua Root > > wrote:
>> 
>> On 2022-7-7 07:40 , Mark Brethen wrote:
>>> The source is a combination of C and fortran, so a C-compiler with 
>>> fortran is needed-preferably gcc. The gcc8 build is the only one that 
>>> does not issue those warnings. But I have successfully run verification 
>>> test cases packaged with the source against gcc8, gcc9, gcc11 and 
>>> gfortran builds.
>>> The compilers PortGroup sets gfortran by default with these settings:
>>> compilers.choosefc cc
>>> compilers.setup require_fortran -g95 -clang
>>> But it uses clang to compile the C-code. I tried blacklisting clang but 
>>> then it wants to install clang-14. Choosing a gcc variant uses its 
>>> associated mp-gfortan compiler.
>> 
>> Yes, +gfortran is there to only give you a fortran compiler (because 
>> clang doesn't have one). Is there a reason you need the C code to be 
>> compiled with gcc?
>> 
>> - Josh
>> 

Re: compilers PortGroup

[Chris Jones]

Ok, shame.

Nevertheless, this is not an issue with the compiler but the code itself. You 
might try discussing it with the upstream maintainers.

Chris

> On 17 Jul 2022, at 3:29 pm, Mark Brethen  wrote:
> 
> Hmm, 'compilers.allow_arguments_mismatch yes’ had no effect—same failure. I 
> looked at the compilers group and with it set, and gfortran variant is 
> selected, chooses ${compilers.gcc_default}. Which in my case was gcc12—which 
> is already installed.
> 
> Mark Brethen
> mark.bret...@gmail.com
> 
> 
> 
>>> On Jul 17, 2022, at 6:15 AM, Chris Jones  wrote:
>>> 
>>> 
>>> 
 On 17 Jul 2022, at 1:59 am, Mark Brethen  wrote:
 
>>> I’ve tested the build with gfortran-mp-12  which fails:
>>> 
>>> :info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
>>> :info:build gencontelem_n2f.f:595:39:
>>> :info:build   184 |call 
>>> isortii(ialset(istartset(iset)),idummy,
>>> :info:build   |2
>>> :info:build ..
>>> :info:build   595 | call 
>>> isortii(nodef,iorder,nopes,kflag)
>>> :info:build   |   1
>>> :info:build Error: Rank mismatch between actual argument at (1) and actual 
>>> argument at (2) (scalar and rank-1)
>>> :info:build make: *** [gencontelem_n2f.o] Error 1
>>> 
>>> How is a particular value of gfortran blacklisted, in this case 
>>> gfortran-mp-12? 
>> 
>> As Ken has eluded to, this is not a problem with the compiler, but an issue 
>> i. The code itself made apparent by stricter checks in recent compilers. You 
>> will likely run into the same with most recent versions so blacklisting is 
>> not the fix here.
>> 
>> The option Ken mentioned turns off those checks
>> 
>> https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L782
>> 
>> so is definitely the way forward I would think.
>> 
>> Chris
>> 
>>> 
>>> Mark Brethen
>>> mark.bret...@gmail.com
>>> 
>>> 
>>> 
 On Jul 6, 2022, at 10:19 PM, Mark Brethen  wrote:
 
 The Spooles library is written in C language and has multi-threading 
 subroutines.
 
 Mark Brethen
 mark.bret...@gmail.com
 
 
 
>> On Jul 6, 2022, at 5:06 PM, Joshua Root  wrote:
> 
> On 2022-7-7 07:40 , Mark Brethen wrote:
>> The source is a combination of C and fortran, so a C-compiler with 
>> fortran is needed-preferably gcc. The gcc8 build is the only one that 
>> does not issue those warnings. But I have successfully run verification 
>> test cases packaged with the source against gcc8, gcc9, gcc11 and 
>> gfortran builds.
>> The compilers PortGroup sets gfortran by default with these settings:
>> compilers.choosefc cc
>> compilers.setup require_fortran -g95 -clang
>> But it uses clang to compile the C-code. I tried blacklisting clang but 
>> then it wants to install clang-14. Choosing a gcc variant uses its 
>> associated mp-gfortan compiler.
> 
> Yes, +gfortran is there to only give you a fortran compiler (because 
> clang doesn't have one). Is there a reason you need the C code to be 
> compiled with gcc?
> 
> - Josh
> 

Re: compilers PortGroup

[Mark Brethen]

Hmm, 'compilers.allow_arguments_mismatch yes’ had no effect—same failure. I 
looked at the compilers group and with it set, and gfortran variant is 
selected, chooses ${compilers.gcc_default}. Which in my case was gcc12—which is 
already installed.

Mark Brethen
mark.bret...@gmail.com



> On Jul 17, 2022, at 6:15 AM, Chris Jones  wrote:
> 
> 
> 
>> On 17 Jul 2022, at 1:59 am, Mark Brethen  wrote:
>> 
>> I’ve tested the build with gfortran-mp-12  which fails:
>> 
>> :info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
>> :info:build gencontelem_n2f.f:595:39:
>> :info:build   184 |call 
>> isortii(ialset(istartset(iset)),idummy,
>> :info:build   |2
>> :info:build ..
>> :info:build   595 | call 
>> isortii(nodef,iorder,nopes,kflag)
>> :info:build   |   1
>> :info:build Error: Rank mismatch between actual argument at (1) and actual 
>> argument at (2) (scalar and rank-1)
>> :info:build make: *** [gencontelem_n2f.o] Error 1
>> 
>> How is a particular value of gfortran blacklisted, in this case 
>> gfortran-mp-12? 
> 
> As Ken has eluded to, this is not a problem with the compiler, but an issue 
> i. The code itself made apparent by stricter checks in recent compilers. You 
> will likely run into the same with most recent versions so blacklisting is 
> not the fix here.
> 
> The option Ken mentioned turns off those checks
> 
> https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L782
>  
> 
> 
> so is definitely the way forward I would think.
> 
> Chris
> 
>> 
>> Mark Brethen
>> mark.bret...@gmail.com
>> 
>> 
>> 
>>> On Jul 6, 2022, at 10:19 PM, Mark Brethen  wrote:
>>> 
>>> The Spooles library is written in C language and has multi-threading 
>>> subroutines.
>>> 
>>> Mark Brethen
>>> mark.bret...@gmail.com
>>> 
>>> 
>>> 
 On Jul 6, 2022, at 5:06 PM, Joshua Root  wrote:
 
 On 2022-7-7 07:40 , Mark Brethen wrote:
> The source is a combination of C and fortran, so a C-compiler with 
> fortran is needed-preferably gcc. The gcc8 build is the only one that 
> does not issue those warnings. But I have successfully run verification 
> test cases packaged with the source against gcc8, gcc9, gcc11 and 
> gfortran builds.
> The compilers PortGroup sets gfortran by default with these settings:
> compilers.choosefc cc
> compilers.setup require_fortran -g95 -clang
> But it uses clang to compile the C-code. I tried blacklisting clang but 
> then it wants to install clang-14. Choosing a gcc variant uses its 
> associated mp-gfortan compiler.
 
 Yes, +gfortran is there to only give you a fortran compiler (because clang 
 doesn't have one). Is there a reason you need the C code to be compiled 
 with gcc?
 
 - Josh

Re: compilers PortGroup

[Chris Jones]

> On 17 Jul 2022, at 1:59 am, Mark Brethen  wrote:
> 
> I’ve tested the build with gfortran-mp-12  which fails:
> 
> :info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
> :info:build gencontelem_n2f.f:595:39:
> :info:build   184 |call 
> isortii(ialset(istartset(iset)),idummy,
> :info:build   |2
> :info:build ..
> :info:build   595 | call isortii(nodef,iorder,nopes,kflag)
> :info:build   |   1
> :info:build Error: Rank mismatch between actual argument at (1) and actual 
> argument at (2) (scalar and rank-1)
> :info:build make: *** [gencontelem_n2f.o] Error 1
> 
> How is a particular value of gfortran blacklisted, in this case 
> gfortran-mp-12? 

As Ken has eluded to, this is not a problem with the compiler, but an issue i. 
The code itself made apparent by stricter checks in recent compilers. You will 
likely run into the same with most recent versions so blacklisting is not the 
fix here.

The option Ken mentioned turns off those checks

https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L782

so is definitely the way forward I would think.

Chris

> 
> Mark Brethen
> mark.bret...@gmail.com
> 
> 
> 
>> On Jul 6, 2022, at 10:19 PM, Mark Brethen  wrote:
>> 
>> The Spooles library is written in C language and has multi-threading 
>> subroutines.
>> 
>> Mark Brethen
>> mark.bret...@gmail.com
>> 
>> 
>> 
 On Jul 6, 2022, at 5:06 PM, Joshua Root  wrote:
>>> 
>>> On 2022-7-7 07:40 , Mark Brethen wrote:
 The source is a combination of C and fortran, so a C-compiler with fortran 
 is needed-preferably gcc. The gcc8 build is the only one that does not 
 issue those warnings. But I have successfully run verification test cases 
 packaged with the source against gcc8, gcc9, gcc11 and gfortran builds.
 The compilers PortGroup sets gfortran by default with these settings:
 compilers.choosefc cc
 compilers.setup require_fortran -g95 -clang
 But it uses clang to compile the C-code. I tried blacklisting clang but 
 then it wants to install clang-14. Choosing a gcc variant uses its 
 associated mp-gfortan compiler.
>>> 
>>> Yes, +gfortran is there to only give you a fortran compiler (because clang 
>>> doesn't have one). Is there a reason you need the C code to be compiled 
>>> with gcc?
>>> 
>>> - Josh
>> 
> 

Re: compilers PortGroup

[Ken Cunningham]

> :info:build 595 | call isortii(nodef,iorder,nopes,kflag) 
> :info:build | 1 
> :info:build Error: Rank mismatch between actual argument at (1) and actual 
> argument at (2) (scalar and rank-1) 
> :info:build make: *** [gencontelem_n2f.o] Error 1 

perhaps it might be worth trying this option?

compilers.allow_arguments_mismatch


https://github.com/macports/macports-ports/blob/8f07e286eac6e7fa7c9bcd282cc461ee945c7c8d/_resources/port1.0/group/compilers-1.0.tcl#L49

Re: compilers PortGroup

[Mark Brethen]

I’ve tested the build with gfortran-mp-12  which fails:

:info:build /opt/local/bin/gfortran-mp-12 -Wall -O2 -c gencontelem_n2f.f
:info:build gencontelem_n2f.f:595:39:
:info:build   184 |call isortii(ialset(istartset(iset)),idummy,
:info:build   |2
:info:build ..
:info:build   595 | call isortii(nodef,iorder,nopes,kflag)
:info:build   |   1
:info:build Error: Rank mismatch between actual argument at (1) and actual 
argument at (2) (scalar and rank-1)
:info:build make: *** [gencontelem_n2f.o] Error 1

How is a particular value of gfortran blacklisted, in this case gfortran-mp-12? 

Mark Brethen
mark.bret...@gmail.com



> On Jul 6, 2022, at 10:19 PM, Mark Brethen  wrote:
> 
> The Spooles library is written in C language and has multi-threading 
> subroutines.
> 
> Mark Brethen
> mark.bret...@gmail.com
> 
> 
> 
>> On Jul 6, 2022, at 5:06 PM, Joshua Root  wrote:
>> 
>> On 2022-7-7 07:40 , Mark Brethen wrote:
>>> The source is a combination of C and fortran, so a C-compiler with fortran 
>>> is needed-preferably gcc. The gcc8 build is the only one that does not 
>>> issue those warnings. But I have successfully run verification test cases 
>>> packaged with the source against gcc8, gcc9, gcc11 and gfortran builds.
>>> The compilers PortGroup sets gfortran by default with these settings:
>>> compilers.choosefc cc
>>> compilers.setup require_fortran -g95 -clang
>>> But it uses clang to compile the C-code. I tried blacklisting clang but 
>>> then it wants to install clang-14. Choosing a gcc variant uses its 
>>> associated mp-gfortan compiler.
>> 
>> Yes, +gfortran is there to only give you a fortran compiler (because clang 
>> doesn't have one). Is there a reason you need the C code to be compiled with 
>> gcc?
>> 
>> - Josh
> 

Re: compilers PortGroup

[Mark Brethen]

The Spooles library is written in C language and has multi-threading 
subroutines.

Mark Brethen
mark.bret...@gmail.com



> On Jul 6, 2022, at 5:06 PM, Joshua Root  wrote:
> 
> On 2022-7-7 07:40 , Mark Brethen wrote:
>> The source is a combination of C and fortran, so a C-compiler with fortran 
>> is needed-preferably gcc. The gcc8 build is the only one that does not issue 
>> those warnings. But I have successfully run verification test cases packaged 
>> with the source against gcc8, gcc9, gcc11 and gfortran builds.
>> The compilers PortGroup sets gfortran by default with these settings:
>> compilers.choosefc cc
>> compilers.setup require_fortran -g95 -clang
>> But it uses clang to compile the C-code. I tried blacklisting clang but then 
>> it wants to install clang-14. Choosing a gcc variant uses its associated 
>> mp-gfortan compiler.
> 
> Yes, +gfortran is there to only give you a fortran compiler (because clang 
> doesn't have one). Is there a reason you need the C code to be compiled with 
> gcc?
> 
> - Josh

Re: compilers PortGroup

[Joshua Root]

On 2022-7-7 07:40 , Mark Brethen wrote:
The source is a combination of C and fortran, so a C-compiler with 
fortran is needed-preferably gcc. The gcc8 build is the only one that 
does not issue those warnings. But I have successfully run verification 
test cases packaged with the source against gcc8, gcc9, gcc11 and 
gfortran builds.


The compilers PortGroup sets gfortran by default with these settings:

compilers.choose    fc cc
compilers.setup     require_fortran -g95 -clang

But it uses clang to compile the C-code. I tried blacklisting clang but 
then it wants to install clang-14. Choosing a gcc variant uses its 
associated mp-gfortan compiler.


Yes, +gfortran is there to only give you a fortran compiler (because 
clang doesn't have one). Is there a reason you need the C code to be 
compiled with gcc?


- Josh

Re: compilers PortGroup

[Mark Brethen]

The source is a combination of C and fortran, so a C-compiler with fortran is 
needed-preferably gcc. The gcc8 build is the only one that does not issue those 
warnings. But I have successfully run verification test cases packaged with the 
source against gcc8, gcc9, gcc11 and gfortran builds.  

The compilers PortGroup sets gfortran by default with these settings:

compilers.choosefc cc
compilers.setup require_fortran -g95 -clang

But it uses clang to compile the C-code. I tried blacklisting clang but then it 
wants to install clang-14. Choosing a gcc variant uses its associated 
mp-gfortan compiler.





Mark Brethen
mark.bret...@gmail.com



> On Jul 6, 2022, at 2:18 PM, Dave Allured - NOAA Affiliate via macports-dev 
>  wrote:
> 
> Mark, those are specifically fortran issues, not C.  Both of those warnings 
> refer to fortran constructs which were declared obsolescent in fortran 90.  
> That is a long time ago.  However, it looks like your modern gfortran version 
> is still compiling these constructs correctly, but issuing compile time 
> warnings.  This is most appropriate.  If possible, test functionality to 
> ensure that part about "compiling correctly" is not a lie.
> 
> I suggest best practice is to /not/ cover up these warnings with some -std 
> option or other sort of patch.  If the build works, then leave the warnings 
> in place for future benefit.  For best results, request an upstream fix to 
> replace these deleted constructs with more modern constructs, or submit your 
> own upstream fix.  Both fixes are straightforward fortran.
> 
> 
> On Tue, Jul 5, 2022 at 9:22 PM Mark Brethen  > wrote:
> I have the compiler.setup so that gfortran is selected by default, however 
> checking the build log I’m seeing these warning messages:
> 
> Warning: Fortran 2018 deleted feature: DO termination statement which is not 
> END DO or CONTINUE with label 215 at (1)
> 
> Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1)
> 
> Those messages are only warnings. But to side-step these issues, do I need to 
> add the -std option to specify which version of the fortran standard to use 
> when compiling?
> 
> E.g. compiler.c_standard   2008
> 
> Thanks
> Mark
> 
> 
> > On Jul 4, 2022, at 9:36 AM, Mark Brethen  > > wrote:
> > 
> > Sorry for the confusion, 'sudo port build xyx'.
> > 
> > Mark Brethen
> > mark.bret...@gmail.com 
> > 
> > 
> >> On Jul 4, 2022, at 9:07 AM, Joshua Root  >> > wrote:
> >> 
> >> On 2022-7-4 23:24 , Mark Brethen wrote:
> >>> Here’s what I’ve observed:
> >>> compilers.choose fc cc
> >>> compiler.setup  require_fortran -g95 -clang
> >>> If I issue sudo port xyz +gcc11, I get ${configure.cc} = /usr/bin/clang.
> >> 
> >> What is xyz? When are you reading the variable? If it's before the 
> >> variants execute, you won't see the changes they make.
> >> 
> >> - Josh

Re: compilers PortGroup

[Dave Allured - NOAA Affiliate via macports-dev]

Mark, those are specifically fortran issues, not C.  Both of those warnings
refer to fortran constructs which were declared obsolescent in fortran 90.
That is a long time ago.  However, it looks like your modern gfortran
version is still compiling these constructs correctly, but issuing compile
time warnings.  This is most appropriate.  If possible, test functionality
to ensure that part about "compiling correctly" is not a lie.

I suggest best practice is to /not/ cover up these warnings with some -std
option or other sort of patch.  If the build works, then leave the warnings
in place for future benefit.  For best results, request an upstream fix to
replace these deleted constructs with more modern constructs, or submit
your own upstream fix.  Both fixes are straightforward fortran.


On Tue, Jul 5, 2022 at 9:22 PM Mark Brethen  wrote:

> I have the compiler.setup so that gfortran is selected by default, however
> checking the build log I’m seeing these warning messages:
>
> Warning: Fortran 2018 deleted feature: DO termination statement which is
> not END DO or CONTINUE with label 215 at (1)
>
> Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1)
>
> Those messages are only warnings. But to side-step these issues, do I need
> to add the -std option to specify which version of the fortran standard to
> use when compiling?
>
> E.g. compiler.c_standard   2008
>
> Thanks
> Mark
>
>
> > On Jul 4, 2022, at 9:36 AM, Mark Brethen  wrote:
> >
> > Sorry for the confusion, 'sudo port build xyx'.
> >
> > Mark Brethen
> > mark.bret...@gmail.com
> >
> >
> >> On Jul 4, 2022, at 9:07 AM, Joshua Root  wrote:
> >>
> >> On 2022-7-4 23:24 , Mark Brethen wrote:
> >>> Here’s what I’ve observed:
> >>> compilers.choose fc cc
> >>> compiler.setup  require_fortran -g95 -clang
> >>> If I issue sudo port xyz +gcc11, I get ${configure.cc} =
> /usr/bin/clang.
> >>
> >> What is xyz? When are you reading the variable? If it's before the
> variants execute, you won't see the changes they make.
> >>
> >> - Josh
>

Re: compilers PortGroup

[Mark Brethen]

I have the compiler.setup so that gfortran is selected by default, however 
checking the build log I’m seeing these warning messages:

Warning: Fortran 2018 deleted feature: DO termination statement which is not 
END DO or CONTINUE with label 215 at (1)

Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1)


Those messages are only warnings. But to side-step these issues, do I need to 
add the -std option to specify which version of the fortran standard to use 
when compiling?

E.g. compiler.c_standard   2008

Thanks
Mark



> On Jul 4, 2022, at 9:36 AM, Mark Brethen  wrote:
> 
> Sorry for the confusion, 'sudo port build xyx'.
> 
> Mark Brethen
> mark.bret...@gmail.com
> 
> 
> 
>> On Jul 4, 2022, at 9:07 AM, Joshua Root  wrote:
>> 
>> On 2022-7-4 23:24 , Mark Brethen wrote:
>>> Here’s what I’ve observed:
>>> compilers.choose fc cc
>>> compiler.setup  require_fortran -g95 -clang
>>> If I issue sudo port xyz +gcc11, I get ${configure.cc} = /usr/bin/clang.
>> 
>> What is xyz? When are you reading the variable? If it's before the variants 
>> execute, you won't see the changes they make.
>> 
>> - Josh
> 

Re: compilers PortGroup

[Mark Brethen]

Sorry for the confusion, 'sudo port build xyx'.

Mark Brethen
mark.bret...@gmail.com



> On Jul 4, 2022, at 9:07 AM, Joshua Root  wrote:
> 
> On 2022-7-4 23:24 , Mark Brethen wrote:
>> Here’s what I’ve observed:
>> compilers.choose fc cc
>> compiler.setup  require_fortran -g95 -clang
>> If I issue sudo port xyz +gcc11, I get ${configure.cc} = /usr/bin/clang.
> 
> What is xyz? When are you reading the variable? If it's before the variants 
> execute, you won't see the changes they make.
> 
> - Josh

Re: compilers PortGroup

[Joshua Root]

On 2022-7-4 23:24 , Mark Brethen wrote:

Here’s what I’ve observed:

compilers.choose fc cc
compiler.setup  require_fortran -g95 -clang

If I issue sudo port xyz +gcc11, I get ${configure.cc} = /usr/bin/clang.


What is xyz? When are you reading the variable? If it's before the 
variants execute, you won't see the changes they make.


- Josh

Re: compilers PortGroup

[Mark Brethen]

Here’s what I’ve observed:

compilers.choose fc cc
compiler.setup  require_fortran -g95 -clang 

If I issue sudo port xyz +gcc11, I get ${configure.cc} = /usr/bin/clang.


 


Mark Brethen
mark.bret...@gmail.com



> On Jul 3, 2022, at 4:29 PM, David Strubbe  wrote:
> 
> Hello Mark,
> 
> Don't whitelist a particular one that you think works; blacklist ones that 
> you know don't work.
> Additionally, I wonder if you are actually using the result of the compilers 
> portgroup. You have to tell it to use the compiler from the variants for e.g. 
> CC. See examples on that. If you don't do this, it has no effect on what is 
> used. Yes there are also some subtleties about different versions of 
> compilers as stated here: 
> https://trac.macports.org/wiki/UsingTheRightCompiler 
> 
> 
> David
> 
> On Sun, Jul 3, 2022 at 2:16 PM Mark Brethen  > wrote:
> Having looked at the examples, this one is similar to what I tried (and fails 
> to build):
> 
> compilers.choosefc cc
> compilers.setup require_fortran -g95 -clang
> 
> :info:build make: *** [ccx_2.18.a] Error 1
> :info:build make: Leaving directory 
> `/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src'
> :info:build Command failed:  cd 
> "/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src"
>  && /usr/bin/make -j1 -w CC=/usr/bin/clang FC= CFLAGS="-O2 
> -I../../spooles-2.2/ -DARCH=Linux -DSPOOLES -DARPACK -DMATRIXSTORAGE 
> -DUSE_MT=1" DIR="../../spooles-2.2" 
> :info:build Exit code: 2
> :error:build Failed to build CalculiX-ccx: command execution failed
> :debug:build Error code: CHILDSTATUS 48534 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec -callback portprogress::target_progress_callback 
> build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
> 
> 
> whereas adding a whitelist succeeds (using gfortran):
> 
> compiler.whitelist  macports-gcc-11
> compilers.choosefc cc
> compilers.setup require_fortran -g95 -clang
> 
> Is this a difference between mp and apple gcc?
> 
> 
> Mark Brethen
> mark.bret...@gmail.com 
> 
> 
> 
>> On Jul 3, 2022, at 2:50 PM, David Strubbe > > wrote:
>> 
>> Hello Mark,
>> 
>> I think you may have a basic misunderstanding here. The compilers portgroup 
>> provides variants that select compilers, rather than being a way to select 
>> the compiler in the portfile. It will provide gcc/gfortran (in specific 
>> versions). If something like clang doesn't work, you remove it from the 
>> variants list. "active_variants" is about compatibility of compilers used by 
>> dependences. As far as I know, variants are definitely still the recommended 
>> way of handling compiler selection. I suggest you look at some examples to 
>> see how to use compilers portgroup. I made many in the science category, 
>> such as octopus, sparskit, berkeleygw, libxc.
>> 
>> David
>> 
>> On Sat, Jul 2, 2022 at 4:20 PM Mark Brethen > > wrote:
>> This port does not have config, so I’m having to pass the build args. How do 
>> I specify a gcc (gfortran) compiler? Clang doesn’t work.
>> 
>> Thanks,
>> Mark
>> 
>> 
>> 
>> > On Jul 2, 2022, at 2:21 PM, Mark Brethen > > > wrote:
>> > 
>> > Still not working…
>> > 
>> > 
>> > 
>> > Mark Brethen
>> > mark.bret...@gmail.com 
>> > 
>> > 
>> > 
>> >> On Jul 2, 2022, at 2:15 PM, Mark Brethen > >> > wrote:
>> >> 
>> >> I should have looked at the active-variants tcl:
>> >> 
>> >> require_active_variants arpack accelerate mpich
>> >> 
>> >> should be
>> >> 
>> >> require_active_variants arpack "accelerate mpich"
>> >> 
>> >> Mark Brethen
>> >> mark.bret...@gmail.com 
>> >> 
>> >> 
>> >> 
>> >>> On Jul 2, 2022, at 1:48 PM, Mark Brethen > >>> > wrote:
>> >>> 
>> >>> Attaching log
>> >>> 
>> >>> 
>> >>> Mark
>> >>> 
>> >>> 
>> >>> 
>>  On Jul 2, 2022, at 9:22 AM, Mark Brethen >  > wrote:
>>  
>>  I looked at the compilers PortGroup tcl but can’t figure out how to set 
>>  up gcc (for gfortran). I tried setting "compilers.choose cc” and 
>>  “compilers.setup require_fortran” but it continues to use clang.
>>  
>>  Thanks
>>  Mark
>>  
>>  
>> >>> 
>> >> 
>> > 
>> 
> 

Re: compilers PortGroup

[David Strubbe]

Hello Mark,

Don't whitelist a particular one that you think works; blacklist ones that
you know don't work.
Additionally, I wonder if you are actually using the result of the
compilers portgroup. You have to tell it to use the compiler from the
variants for e.g. CC. See examples on that. If you don't do this, it has no
effect on what is used. Yes there are also some subtleties about different
versions of compilers as stated here:
https://trac.macports.org/wiki/UsingTheRightCompiler

David

On Sun, Jul 3, 2022 at 2:16 PM Mark Brethen  wrote:

> Having looked at the examples, this one is similar to what I tried (and
> fails to build):
>
> compilers.choosefc cc
> compilers.setup require_fortran -g95 -clang
>
> :info:build make: *** [ccx_2.18.a] Error 1
> :info:build make: Leaving directory
> `/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src'
> :info:build Command failed:  cd
> "/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src"
> && /usr/bin/make -j1 -w CC=/usr/bin/clang FC= CFLAGS="-O2
> -I../../spooles-2.2/ -DARCH=Linux -DSPOOLES -DARPACK -DMATRIXSTORAGE
> -DUSE_MT=1" DIR="../../spooles-2.2"
> :info:build Exit code: 2
> :error:build Failed to build CalculiX-ccx: command execution failed
> :debug:build Error code: CHILDSTATUS 48534 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec -callback
> portprogress::target_progress_callback build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
>
>
> whereas adding a whitelist succeeds (using gfortran):
>
> compiler.whitelist  macports-gcc-11
> compilers.choosefc cc
> compilers.setup require_fortran -g95 -clang
>
> Is this a difference between mp and apple gcc?
>
>
> Mark Brethen
> mark.bret...@gmail.com
>
>
>
> On Jul 3, 2022, at 2:50 PM, David Strubbe  wrote:
>
> Hello Mark,
>
> I think you may have a basic misunderstanding here. The compilers
> portgroup provides variants that select compilers, rather than being a way
> to select the compiler in the portfile. It will provide gcc/gfortran (in
> specific versions). If something like clang doesn't work, you remove it
> from the variants list. "active_variants" is about compatibility of
> compilers used by dependences. As far as I know, variants are definitely
> still the recommended way of handling compiler selection. I suggest you
> look at some examples to see how to use compilers portgroup. I made many in
> the science category, such as octopus, sparskit, berkeleygw, libxc.
>
> David
>
> On Sat, Jul 2, 2022 at 4:20 PM Mark Brethen 
> wrote:
>
>> This port does not have config, so I’m having to pass the build args. How
>> do I specify a gcc (gfortran) compiler? Clang doesn’t work.
>>
>> Thanks,
>> Mark
>>
>>
>>
>> > On Jul 2, 2022, at 2:21 PM, Mark Brethen 
>> wrote:
>> >
>> > Still not working…
>> > 
>> >
>> >
>> > Mark Brethen
>> > mark.bret...@gmail.com
>> >
>> >
>> >
>> >> On Jul 2, 2022, at 2:15 PM, Mark Brethen 
>> wrote:
>> >>
>> >> I should have looked at the active-variants tcl:
>> >>
>> >> require_active_variants arpack accelerate mpich
>> >>
>> >> should be
>> >>
>> >> require_active_variants arpack "accelerate mpich"
>> >>
>> >> Mark Brethen
>> >> mark.bret...@gmail.com
>> >>
>> >>
>> >>
>> >>> On Jul 2, 2022, at 1:48 PM, Mark Brethen 
>> wrote:
>> >>>
>> >>> Attaching log
>> >>> 
>> >>>
>> >>> Mark
>> >>>
>> >>>
>> >>>
>>  On Jul 2, 2022, at 9:22 AM, Mark Brethen 
>> wrote:
>> 
>>  I looked at the compilers PortGroup tcl but can’t figure out how to
>> set up gcc (for gfortran). I tried setting "compilers.choose cc” and
>> “compilers.setup require_fortran” but it continues to use clang.
>> 
>>  Thanks
>>  Mark
>> 
>> 
>> >>>
>> >>
>> >
>>
>>
>

Re: compilers PortGroup

[Mark Brethen]

Having looked at the examples, this one is similar to what I tried (and fails 
to build):

compilers.choosefc cc
compilers.setup require_fortran -g95 -clang

:info:build make: *** [ccx_2.18.a] Error 1
:info:build make: Leaving directory 
`/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src'
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_Users_marbre_ports_cad_CalculiX-ccx/CalculiX-ccx/work/ccx_2.18/src"
 && /usr/bin/make -j1 -w CC=/usr/bin/clang FC= CFLAGS="-O2 -I../../spooles-2.2/ 
-DARCH=Linux -DSPOOLES -DARPACK -DMATRIXSTORAGE -DUSE_MT=1" 
DIR="../../spooles-2.2" 
:info:build Exit code: 2
:error:build Failed to build CalculiX-ccx: command execution failed
:debug:build Error code: CHILDSTATUS 48534 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback 
build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"


whereas adding a whitelist succeeds (using gfortran):

compiler.whitelist  macports-gcc-11
compilers.choosefc cc
compilers.setup require_fortran -g95 -clang

Is this a difference between mp and apple gcc?


Mark Brethen
mark.bret...@gmail.com



> On Jul 3, 2022, at 2:50 PM, David Strubbe  wrote:
> 
> Hello Mark,
> 
> I think you may have a basic misunderstanding here. The compilers portgroup 
> provides variants that select compilers, rather than being a way to select 
> the compiler in the portfile. It will provide gcc/gfortran (in specific 
> versions). If something like clang doesn't work, you remove it from the 
> variants list. "active_variants" is about compatibility of compilers used by 
> dependences. As far as I know, variants are definitely still the recommended 
> way of handling compiler selection. I suggest you look at some examples to 
> see how to use compilers portgroup. I made many in the science category, such 
> as octopus, sparskit, berkeleygw, libxc.
> 
> David
> 
> On Sat, Jul 2, 2022 at 4:20 PM Mark Brethen  > wrote:
> This port does not have config, so I’m having to pass the build args. How do 
> I specify a gcc (gfortran) compiler? Clang doesn’t work.
> 
> Thanks,
> Mark
> 
> 
> 
> > On Jul 2, 2022, at 2:21 PM, Mark Brethen  > > wrote:
> > 
> > Still not working…
> > 
> > 
> > 
> > Mark Brethen
> > mark.bret...@gmail.com 
> > 
> > 
> > 
> >> On Jul 2, 2022, at 2:15 PM, Mark Brethen  >> > wrote:
> >> 
> >> I should have looked at the active-variants tcl:
> >> 
> >> require_active_variants arpack accelerate mpich
> >> 
> >> should be
> >> 
> >> require_active_variants arpack "accelerate mpich"
> >> 
> >> Mark Brethen
> >> mark.bret...@gmail.com 
> >> 
> >> 
> >> 
> >>> On Jul 2, 2022, at 1:48 PM, Mark Brethen  >>> > wrote:
> >>> 
> >>> Attaching log
> >>> 
> >>> 
> >>> Mark
> >>> 
> >>> 
> >>> 
>  On Jul 2, 2022, at 9:22 AM, Mark Brethen   > wrote:
>  
>  I looked at the compilers PortGroup tcl but can’t figure out how to set 
>  up gcc (for gfortran). I tried setting "compilers.choose cc” and 
>  “compilers.setup require_fortran” but it continues to use clang.
>  
>  Thanks
>  Mark
>  
>  
> >>> 
> >> 
> > 
> 

Re: compilers PortGroup

[David Strubbe]

Hello Mark,

I think you may have a basic misunderstanding here. The compilers portgroup
provides variants that select compilers, rather than being a way to select
the compiler in the portfile. It will provide gcc/gfortran (in specific
versions). If something like clang doesn't work, you remove it from the
variants list. "active_variants" is about compatibility of compilers used
by dependences. As far as I know, variants are definitely still the
recommended way of handling compiler selection. I suggest you look at some
examples to see how to use compilers portgroup. I made many in the science
category, such as octopus, sparskit, berkeleygw, libxc.

David

On Sat, Jul 2, 2022 at 4:20 PM Mark Brethen  wrote:

> This port does not have config, so I’m having to pass the build args. How
> do I specify a gcc (gfortran) compiler? Clang doesn’t work.
>
> Thanks,
> Mark
>
>
>
> > On Jul 2, 2022, at 2:21 PM, Mark Brethen  wrote:
> >
> > Still not working…
> > 
> >
> >
> > Mark Brethen
> > mark.bret...@gmail.com
> >
> >
> >
> >> On Jul 2, 2022, at 2:15 PM, Mark Brethen 
> wrote:
> >>
> >> I should have looked at the active-variants tcl:
> >>
> >> require_active_variants arpack accelerate mpich
> >>
> >> should be
> >>
> >> require_active_variants arpack "accelerate mpich"
> >>
> >> Mark Brethen
> >> mark.bret...@gmail.com
> >>
> >>
> >>
> >>> On Jul 2, 2022, at 1:48 PM, Mark Brethen 
> wrote:
> >>>
> >>> Attaching log
> >>> 
> >>>
> >>> Mark
> >>>
> >>>
> >>>
>  On Jul 2, 2022, at 9:22 AM, Mark Brethen 
> wrote:
> 
>  I looked at the compilers PortGroup tcl but can’t figure out how to
> set up gcc (for gfortran). I tried setting "compilers.choose cc” and
> “compilers.setup require_fortran” but it continues to use clang.
> 
>  Thanks
>  Mark
> 
> 
> >>>
> >>
> >
>
>

Re: compilers PortGroup

[Mark Brethen]

This port does not have config, so I’m having to pass the build args. How do I 
specify a gcc (gfortran) compiler? Clang doesn’t work.

Thanks,
Mark



> On Jul 2, 2022, at 2:21 PM, Mark Brethen  wrote:
> 
> Still not working…
> 
> 
> 
> Mark Brethen
> mark.bret...@gmail.com
> 
> 
> 
>> On Jul 2, 2022, at 2:15 PM, Mark Brethen  wrote:
>> 
>> I should have looked at the active-variants tcl:
>> 
>> require_active_variants arpack accelerate mpich
>> 
>> should be
>> 
>> require_active_variants arpack "accelerate mpich"
>> 
>> Mark Brethen
>> mark.bret...@gmail.com
>> 
>> 
>> 
>>> On Jul 2, 2022, at 1:48 PM, Mark Brethen  wrote:
>>> 
>>> Attaching log
>>> 
>>> 
>>> Mark
>>> 
>>> 
>>> 
 On Jul 2, 2022, at 9:22 AM, Mark Brethen  wrote:
 
 I looked at the compilers PortGroup tcl but can’t figure out how to set up 
 gcc (for gfortran). I tried setting "compilers.choose cc” and 
 “compilers.setup require_fortran” but it continues to use clang.
 
 Thanks
 Mark
 
 
>>> 
>> 
> 

Re: compilers PortGroup

[Mark Brethen]

I should have looked at the active-variants tcl:

require_active_variants arpack accelerate mpich

should be

require_active_variants arpack "accelerate mpich"

Mark Brethen
mark.bret...@gmail.com



> On Jul 2, 2022, at 1:48 PM, Mark Brethen  wrote:
> 
> Attaching log
> 
> 
> Mark
> 
> 
> 
>> On Jul 2, 2022, at 9:22 AM, Mark Brethen  wrote:
>> 
>> I looked at the compilers PortGroup tcl but can’t figure out how to set up 
>> gcc (for gfortran). I tried setting "compilers.choose cc” and 
>> “compilers.setup require_fortran” but it continues to use clang.
>> 
>> Thanks
>> Mark
>> 
>> 
> 

Re: compilers PortGroup

[Mark Brethen]

Attaching log


main.log
Description: Binary data


Mark



> On Jul 2, 2022, at 9:22 AM, Mark Brethen  wrote:
> 
> I looked at the compilers PortGroup tcl but can’t figure out how to set up 
> gcc (for gfortran). I tried setting "compilers.choose cc” and 
> “compilers.setup require_fortran” but it continues to use clang.
> 
> Thanks
> Mark
> 
>