Sent from my iPhone
> On Aug 27, 2019, at 3:53 AM, Chris Jones <[email protected]> wrote:
>
>
>
>> On 27/08/2019 12:36 am, Mark Brethen wrote:
>> ---> Computing dependencies for arpack
>> ---> Fetching distfiles for arpack
>> Warning: Your DNS servers incorrectly claim to know the address of
>> nonexistent hosts. This may cause checksum mismatches for some ports. See
>> this page for more information:
>> <https://trac.macports.org/wiki/MisbehavingServers>
>> ---> Attempting to fetch arpack-ng-3.7.0.tar.gz from
>> https://distfiles.macports.org/arpack
>> ---> Verifying checksums for arpack
>> ---> Extracting arpack
>> ---> Applying patches to arpack
>> ---> Configuring arpack
>> Error: mpich-default has a different Fortran variant (gcc8) than the one
>> selected, gcc9 (via +gfortran).
>> Error: Failed to configure arpack: Install mpich-default +gcc9
>> Error: See
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_arpack/arpack/main.log
>> for details.
>> E
>> The mpich upgrade broke arpack. How do I recover from this?
>
> Do what it says. Install arpack and mpich-default with the same fortran
> variants.
>
> Most probably you have mpich-default installed with the older gcc8 variant
> active, so just uninstall it and then reinstall with the new default, which
> is gcc9.
>
> Chris
It’s not that simple, there are several dependent ports that were built to the
gcc8 variant. Why did the default gcc change in the first place?