On Tue, Aug 27, 2019 at 02:53:03PM +0100, Chris Jones wrote:
> Ball is in your court to fix this.
Serving suggestion: rather than rip-and-replace, it may be worth using
"port upgrade --enforce-variants offending_port +gcc9 +other_variants"
to change the variants in-place. We use that trick on a
gcc9 default the default when it was release, last year.
Its up to you what you do here. either use gcc8, or gcc9. not a mixture of both.
Chris
If the port was built with the gcc8 variant, ‘port upgrade outdated’ shouldn’t
change that. Doesn’t make sense.
That is exactly the problem.
Sent from my iPhone
> On Aug 27, 2019, at 8:13 AM, Chris Jones wrote:
>
>
>>> 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
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
Sent from my iPhone
> On Aug 27, 2019, at 3:53 AM, Chris Jones 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
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
---> 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:
