>
Extracting
/home/vi/Documents/moose/packages/projects/src/petsc-3.7.6/arch-linux2-c-opt/externalpackages/_d_v5.1.0-p4.tar.gz
<<
Check for 'petsc-pkg-metis' is correct - when the dir is
'petsc-pkg-metis-0adf3ea7785d'.
Looks like this issue was introduced in : v3.7.6 -
The tarball creates a file petsc-pkg-metis-0adf3ea7785d which we do not check
for.
Looks like maint checks for the directory named petsc-pkg-metis
Exactly how did you obtain the metis tarball?
I will check this if it is not resolved later today. Flying back from the
PETSc meeting now
The tarball creates a file petsc-pkg-metis-0adf3ea7785d which we do not check
for.
Looks like maint checks for the directory named petsc-pkg-metis
Exactly how did you obtain the metis tarball?
I will check this if it is not resolved later today. Flying back from the
PETSc meeting
Make sure unzipping v5.1.0-p4.tar.gz generates a directory name started
with metis but not METIS.
--Junchao Zhang
On Wed, Jun 6, 2018 at 10:34 PM, Fande Kong wrote:
> Hi Satish,
>
> A MOOSE user has troubles to build Metis that is "downloaded" from a local
> directory. Do you have any idea?
>
Hi Satish,
A MOOSE user has troubles to build Metis that is "downloaded" from a local
directory. Do you have any idea?
Vi,
Could you share "configure.log" with PETSc team?
Thanks,
Fande,
-- Forwarded message --
From: Vi Ha
Date: Wed, Jun 6, 2018 at 11:00 AM
Subject: Re:
