Re: compilers PortGroup

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:

Re: compilers PortGroup

> 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

Re: compilers PortGroup

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,

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

> 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 >

Re: compilers PortGroup

> :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?

Re: compilers PortGroup

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 |

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

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:

Re: compilers PortGroup

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

Re: compilers PortGroup

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,

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

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

Re: compilers PortGroup

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,

Re: compilers PortGroup

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

Re: compilers PortGroup

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